public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>, [email protected]
Subject: [PATCH liburing 1/3] io_uring_enter.2: add sendzc -EOPNOTSUPP note
Date: Fri, 21 Oct 2022 14:10:58 +0100	[thread overview]
Message-ID: <dfe582705c8c3458f14c6d7f0db9a8bbd371f749.1666357688.git.asml.silence@gmail.com> (raw)
In-Reply-To: <[email protected]>

Signed-off-by: Pavel Begunkov <[email protected]>
---
 man/io_uring_enter.2 | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/man/io_uring_enter.2 b/man/io_uring_enter.2
index 2ebc6e3..25fdc1e 100644
--- a/man/io_uring_enter.2
+++ b/man/io_uring_enter.2
@@ -1098,8 +1098,11 @@ Available since 5.19.
 Issue the zerocopy equivalent of a
 .BR send(2)
 system call. Similar to IORING_OP_SEND, but tries to avoid making intermediate
-copies of data. Zerocopy execution is not guaranteed and it may fall back to
-copying.
+copies of data. Zerocopy execution is not guaranteed and may fall back to
+copying. The request may also fail with
+.B -EOPNOTSUPP,
+for instance when a protocol doesn't support zerocopy in the first place, in
+which case users are recommended to use copying sends instead.
 
 The
 .I flags
-- 
2.38.0


  reply	other threads:[~2022-10-21 13:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 13:10 [PATCH liburing 0/3] improve sendzc man pages Pavel Begunkov
2022-10-21 13:10 ` Pavel Begunkov [this message]
2022-10-21 13:10 ` [PATCH liburing 2/3] io_uring_enter.2: document IORING_RECVSEND_POLL_FIRST Pavel Begunkov
2022-10-21 13:11 ` [PATCH liburing 3/3] io_uring_enter.2: document IORING_RECVSEND_FIXED_BUF Pavel Begunkov
2022-10-21 14:13 ` [PATCH liburing 0/3] improve sendzc man pages Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dfe582705c8c3458f14c6d7f0db9a8bbd371f749.1666357688.git.asml.silence@gmail.com \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox