From: Keith Busch <[email protected]>
To: <[email protected]>, <[email protected]>,
<[email protected]>
Cc: <[email protected]>, <[email protected]>, <[email protected]>,
<[email protected]>, <[email protected]>,
Keith Busch <[email protected]>
Subject: [PATCHv4 0/4] block integrity: directly map user space addresses
Date: Tue, 28 Nov 2023 14:27:48 -0800 [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, falling back to a kernel
bounce buffer if necessary.
v3->v4:
Code organization suggestions (Jens, Christoph)
Spelling and unnecessary punctionation (Anuj)
Open code the final user page unpin (Ming)
Eliminate another allocation for the bounce copy by moving the bvec
into the bip rather than just a pointer to it (me)
Keith Busch (4):
block: bio-integrity: directly map user buffers
nvme: use bio_integrity_map_user
iouring: remove IORING_URING_CMD_POLLED
io_uring: remove uring_cmd cookie
block/bio-integrity.c | 203 ++++++++++++++++++++++++++++++++++++++
drivers/nvme/host/ioctl.c | 197 ++++++------------------------------
include/linux/bio.h | 9 ++
include/linux/io_uring.h | 9 +-
io_uring/uring_cmd.c | 1 -
5 files changed, 243 insertions(+), 176 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-28 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 22:27 Keith Busch [this message]
2023-11-28 22:27 ` [PATCHv4 1/4] block: bio-integrity: directly map user buffers Keith Busch
2023-11-29 15:18 ` Kanchan Joshi
2023-11-29 16:35 ` Keith Busch
2023-11-28 22:27 ` [PATCHv4 2/4] nvme: use bio_integrity_map_user Keith Busch
2023-11-28 22:27 ` [PATCHv4 3/4] iouring: remove IORING_URING_CMD_POLLED Keith Busch
2023-11-28 22:27 ` [PATCHv4 4/4] io_uring: remove uring_cmd cookie Keith Busch
2023-11-29 1:37 ` [PATCHv4 0/4] block integrity: directly map user space addresses Martin K. Petersen
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] \
/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