io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Subject: [PATCH liburing 2/2] man: update notes on register quiesce
Date: Sat, 28 Aug 2021 19:30:44 +0100	[thread overview]
Message-ID: <9976eea690c26a86c5f02f7a9b99bd8b58548d3e.1630175370.git.asml.silence@gmail.com> (raw)
In-Reply-To: <cover.1630175370.git.asml.silence@gmail.com>

We don't quiesce rsrc registrations since 5.13, reflect it in the man.

Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
---
 man/io_uring_register.2 | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/man/io_uring_register.2 b/man/io_uring_register.2
index 5326a87..a8479fd 100644
--- a/man/io_uring_register.2
+++ b/man/io_uring_register.2
@@ -88,9 +88,9 @@ then issuing a new call to
 .BR io_uring_register ()
 with the new buffers.
 
-Note that registering buffers will wait for the ring to idle. If the application
-currently has requests in-flight, the registration will wait for those to
-finish before proceeding.
+Note that before 5.13 registering buffers would wait for the ring to idle.
+If the application currently has requests in-flight, the registration will
+wait for those to finish before proceeding.
 
 An application need not unregister buffers explicitly before shutting
 down the io_uring instance. Available since 5.1.
@@ -128,9 +128,9 @@ See
 .B IORING_REGISTER_FILES_UPDATE
 for how to update files in place.
 
-Note that registering files will wait for the ring to idle. If the application
-currently has requests in-flight, the registration will wait for those to
-finish before proceeding. See
+Note that before 5.13 registering files would wait for the ring to idle.
+If the application currently has requests in-flight, the registration will
+wait for those to finish before proceeding. See
 .B IORING_REGISTER_FILES_UPDATE
 for how to update an existing set without that limitation.
 
-- 
2.33.0


  parent reply	other threads:[~2021-08-28 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-28 18:30 [PATCH liburing 0/2] quick man fixes Pavel Begunkov
2021-08-28 18:30 ` [PATCH liburing 1/2] man: fix io_uring_sqe alignment Pavel Begunkov
2021-08-28 18:30 ` Pavel Begunkov [this message]
2021-08-28 19:15 ` [PATCH liburing 0/2] quick man fixes 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=9976eea690c26a86c5f02f7a9b99bd8b58548d3e.1630175370.git.asml.silence@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).