From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCH for-next 0/2] io_uring SQPOLL related
Date: Thu, 3 Sep 2020 18:02:26 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Patch #1 makes it easier to support a fool proof assignment of the
shared SQPOLL data structure, instead of doing it after the fact. Would
also enable some cleanups around the fd install.
Patch #2 enables an application to wait on SQ ring consumption if using
SQPOLL, instead of having to use busy polling for that part. This can
help provide the necessary backpressure when using SQPOLL.
--
Jens Axboe
next reply other threads:[~2020-09-04 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 0:02 Jens Axboe [this message]
[not found] ` <[email protected]>
2020-09-04 0:02 ` [PATCH 1/2] io_uring: separate ring/file creation from descriptor install Jens Axboe
2020-09-04 0:02 ` [PATCH 2/2] io_uring: provide IORING_ENTER_SQ_WAIT for SQPOLL SQ ring waits 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 \
[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