From: Keith Busch <[email protected]>
To: <[email protected]>, <[email protected]>,
<[email protected]>
Cc: <[email protected]>, <[email protected]>, <[email protected]>,
<[email protected]>, Keith Busch <[email protected]>
Subject: [PATCH 0/4] block integrity: direclty map user space addresses
Date: Wed, 18 Oct 2023 08:18:39 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
From: Keith Busch <[email protected]>
Handling passthrough metadata ("integrity") today introduces overhead
and complications that we can avoid if we just map user space addresses
directly. This patch series implements that.
Keith Busch (4):
block: bio-integrity: add support for user buffers
nvme: use bio_integrity_map_user
iouring: remove IORING_URING_CMD_POLLED
io_uring: remove uring_cmd cookie
block/bio-integrity.c | 67 +++++++++++++
drivers/nvme/host/ioctl.c | 174 ++++++----------------------------
include/linux/bio.h | 8 ++
include/linux/io_uring.h | 8 +-
include/uapi/linux/io_uring.h | 2 -
io_uring/uring_cmd.c | 1 -
6 files changed, 104 insertions(+), 156 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-18 15:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 15:18 Keith Busch [this message]
2023-10-18 15:18 ` [PATCH 1/4] block: bio-integrity: add support for user buffers Keith Busch
2023-10-19 5:39 ` Christoph Hellwig
2023-10-21 3:53 ` kernel test robot
2023-10-21 4:13 ` kernel test robot
2023-10-25 12:51 ` Kanchan Joshi
2023-10-25 14:42 ` Keith Busch
2023-10-18 15:18 ` [PATCH 2/4] nvme: use bio_integrity_map_user Keith Busch
2023-10-19 5:40 ` Christoph Hellwig
2023-10-25 13:26 ` Kanchan Joshi
2023-10-18 15:18 ` [PATCH 3/4] iouring: remove IORING_URING_CMD_POLLED Keith Busch
2023-10-19 5:41 ` Christoph Hellwig
2023-10-19 14:43 ` Keith Busch
2023-10-23 6:18 ` Kanchan Joshi
2023-10-18 15:18 ` [PATCH 4/4] io_uring: remove uring_cmd cookie Keith Busch
2023-10-19 5:34 ` [PATCH 0/4] block integrity: direclty map user space addresses Christoph Hellwig
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] \
/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