From: Jens Axboe <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCHSET v2 0/4] Fixups/improvements for iopoll passthrough
Date: Sat, 3 Sep 2022 10:52:30 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
A mix of cleanups and fixes for the passthrough iopoll support.
1) Cleanup the io_uring iopoll checking, making sure we never mix
types.
2) Prep patch for getting local task_work run efficiently for iopoll.
3) Fixup io_uring iopoll for local task_work.
4) Let's not add an ->uring_cmd_iopoll() handler with a type we know
we have to change, once we support batching. And more importantly,
pass in the poll flags.
Since v1:
- Fix some of patch 4 bleeding into patch 1
- Drop nvme patch, add the two io_uring iopoll patches instead
--
Jens Axboe
next reply other threads:[~2022-09-03 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 16:52 Jens Axboe [this message]
2022-09-03 16:52 ` [PATCH 1/4] io_uring: cleanly separate request types for iopoll Jens Axboe
2022-09-04 15:44 ` Kanchan Joshi
2022-09-03 16:52 ` [PATCH 2/4] io_uring: add local task_work run helper that is entered locked Jens Axboe
2022-09-03 16:52 ` [PATCH 3/4] io_uring: ensure iopoll runs local task work as well Jens Axboe
2022-09-03 16:52 ` [PATCH 4/4] fs: add batch and poll flags to the uring_cmd_iopoll() handler Jens Axboe
2022-09-04 15:50 ` Kanchan Joshi
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] \
[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