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 3/3] io_uring_enter.2: document IORING_RECVSEND_FIXED_BUF
Date: Fri, 21 Oct 2022 14:11:00 +0100	[thread overview]
Message-ID: <2075ca0ba4b2e8bf11cc16131e09ab5136953155.1666357688.git.asml.silence@gmail.com> (raw)
In-Reply-To: <[email protected]>

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

diff --git a/man/io_uring_enter.2 b/man/io_uring_enter.2
index d98ae59..2a8705f 100644
--- a/man/io_uring_enter.2
+++ b/man/io_uring_enter.2
@@ -1231,6 +1231,12 @@ This initial send attempt can be wasteful for the case where the socket
 is expected to be full, setting this flag will bypass the initial send
 attempt and go straight to arming poll. If poll does indicate that data can
 be sent, the operation will proceed.
+
+.B IORING_RECVSEND_FIXED_BUF
+instructs to use a pre-mapped buffer. If set, the
+.I buf_index
+field should contain an index into an array of fixed buffers. See
+io_uring_register(2) for details on how to setup a context for fixed buffer I/O.
 .EE
 .in
 .PP
-- 
2.38.0


  parent 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 ` [PATCH liburing 1/3] io_uring_enter.2: add sendzc -EOPNOTSUPP note Pavel Begunkov
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 ` Pavel Begunkov [this message]
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=2075ca0ba4b2e8bf11cc16131e09ab5136953155.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