From: Breno Leitao <[email protected]>
To: [email protected], [email protected],
[email protected], [email protected]
Cc: [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected]
Subject: [PATCH 0/2] io_uring: Pass whole sqe to commands
Date: Wed, 19 Apr 2023 03:29:28 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
These two patches prepares for the sock support in the io_uring cmd, as
described in the following RFC:
https://lore.kernel.org/lkml/[email protected]/
Since the support described above depends on other refactors, such as the sock
ioctl() sock refactor[1], I would like to start integrating patches that have
consensus and can bring value right now. This will also reduce the patchset
size later.
Regarding to these two patches, they are simple changes that turn io_uring cmd
subsystem more flexible (by passing the whole SQE to the command), and cleaning up an
unnecessary compile check.
These patches were tested by creating a filesyste and mounting an NVME disk
using ubdsrv/ublkb0.
[1] https://lore.kernel.org/lkml/[email protected]/
Breno Leitao (2):
io_uring: Pass whole sqe to commands
io_uring: Remove unnecessary BUILD_BUG_ON
drivers/block/ublk_drv.c | 24 ++++++++++++------------
drivers/nvme/host/ioctl.c | 2 +-
include/linux/io_uring.h | 2 +-
io_uring/opdef.c | 2 +-
io_uring/uring_cmd.c | 14 ++++++--------
io_uring/uring_cmd.h | 8 --------
6 files changed, 21 insertions(+), 31 deletions(-)
--
2.34.1
next reply other threads:[~2023-04-19 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 10:29 Breno Leitao [this message]
2023-04-19 10:29 ` [PATCH 1/2] io_uring: Pass whole sqe to commands Breno Leitao
2023-04-20 4:57 ` Christoph Hellwig
2023-04-20 12:29 ` Breno Leitao
2023-04-20 12:31 ` Christoph Hellwig
2023-04-20 12:38 ` Breno Leitao
2023-04-20 12:46 ` Christoph Hellwig
2023-04-30 14:37 ` Breno Leitao
2023-04-21 15:11 ` Breno Leitao
2023-04-24 5:08 ` Christoph Hellwig
2023-04-19 10:29 ` [PATCH 2/2] io_uring: Remove unnecessary BUILD_BUG_ON Breno Leitao
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] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[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