diff options
| author | nick black <[email protected]> | 2023-02-23 21:29:16 -0500 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2023-02-24 18:31:31 -0800 |
| commit | bce90459937376b6c7553cfbe957d73293ab7bc8 (patch) | |
| tree | 3328869555f157fe025f9b9b630c87cbbd27fcad | |
| parent | 766d1bdceb3290f83ecadd949cc0cd3ef08f8146 (diff) | |
docs: net: fix inaccuracies in msg_zerocopy.rst
Replace "sendpage" with "sendfile". Remove comment about
ENOBUFS when the sockopt hasn't been set; experimentation
indicates that this is not true.
Signed-off-by: nick black <[email protected]>
Reviewed-by: Willem de Bruijn <[email protected]>
Link: https://lore.kernel.org/r/Y/gg/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
| -rw-r--r-- | Documentation/networking/msg_zerocopy.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/networking/msg_zerocopy.rst b/Documentation/networking/msg_zerocopy.rst index 15920db8d35d..b3ea96af9b49 100644 --- a/Documentation/networking/msg_zerocopy.rst +++ b/Documentation/networking/msg_zerocopy.rst @@ -15,7 +15,7 @@ Opportunity and Caveats Copying large buffers between user process and kernel can be expensive. Linux supports various interfaces that eschew copying, -such as sendpage and splice. The MSG_ZEROCOPY flag extends the +such as sendfile and splice. The MSG_ZEROCOPY flag extends the underlying copy avoidance mechanism to common socket send calls. Copy avoidance is not a free lunch. As implemented, with page pinning, @@ -83,8 +83,8 @@ Pass the new flag. ret = send(fd, buf, sizeof(buf), MSG_ZEROCOPY); A zerocopy failure will return -1 with errno ENOBUFS. This happens if -the socket option was not set, the socket exceeds its optmem limit or -the user exceeds its ulimit on locked pages. +the socket exceeds its optmem limit or the user exceeds their ulimit on +locked pages. Mixing copy avoidance and copying |