[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y/gg/EhIIjugLdd3@schwarzgerat.orthanc>
Date: Thu, 23 Feb 2023 21:29:16 -0500
From: nick black <dankamongmen@...il.com>
To: netdev@...r.kernel.org
Cc: Willem de Bruijn <willemb@...gle.com>
Subject: [PATCH] [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 <dankamongmen@...il.com>
---
Documentation/networking/msg_zerocopy.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git Documentation/networking/msg_zerocopy.rst Documentation/networking/msg_zerocopy.rst
index 15920db8d35d..b3ea96af9b49 100644
--- Documentation/networking/msg_zerocopy.rst
+++ 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
--
2.39.1
Powered by blists - more mailing lists