1
81%
master: 81%

Ran 18 Jan 2024 10:11PM UTC

Files 35

Run time 1s

Badge

Embed ▾

Committed 18 Jan 2024 09:41PM UTC coverage: 81.035% (-0.02%) from 81.055%

Job # 7576301678.1

Build Type

push

github

Committed by

azat

Commit Message

Use read/write instead of readv/writev for single buffer

The `readv`/`writev` functions are designed for scattered I/O optimally,
their logic in the kernel is more sophisticated, compared to read/write,
which includes extra on-stack `iovec` in the kernel space, importing `iovec`
array from user space to kernel space, reading/writing with `iov_iter`, etc.
As a result, using `readv`/`writev` on single-segment `iovec` will fall into
the special branch in the kernel where it is imported as `ITER_UBUF` differed
from `ITER_IOVEC` for multiple-segments `iovec`.

Thus, it is just not worth calling `readv`/`writev` for single-segment `iovec`,
we should use `read`/`write` instead, to save it from going through the
sophisticated yet unnecessary kernel code path, circumvent a waste of
kernel on-stack memory, copying `iovec` between user space and kernel space, etc.

Run Details

12797 of 15792 relevant lines covered (81.03%)

555581.01 hits per line

libevent / libevent / 7576301678 / 1
81%
master: 81%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 7576301678.1

libevent / libevent / 7576301678 / 1 81% master: 81%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 7576301678.1

libevent / libevent / 7576301678 / 1
81%
master: 81%

README BADGES
x