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: [PATCHv3 0/5] block integrity: directly map user space addresses
Date: Mon, 20 Nov 2023 14:40:53 -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.
v2->v3:
Introduces a multi-page bvec iterator.
Fix leaking pinned user pages (Kanchan)
Fix final unpaired 'put' on user pages (Kanchan)
Doesn't increase the size of 'struct bio_integrity_profile'; if the
'copy_vec' pointer is needed, it gets appended to the existing bvec.
Fix compiler warnings
Fix compiler error for !CONFIG_BLK_INTEGRITY
Keith Busch (5):
bvec: introduce multi-page bvec iterating
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 | 212 ++++++++++++++++++++++++++++++++++++++
drivers/nvme/host/ioctl.c | 197 ++++++-----------------------------
include/linux/bio.h | 12 +++
include/linux/bvec.h | 6 ++
include/linux/io_uring.h | 9 +-
io_uring/uring_cmd.c | 1 -
6 files changed, 261 insertions(+), 176 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-20 22:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 22:40 Keith Busch [this message]
2023-11-20 22:40 ` [PATCHv3 1/5] bvec: introduce multi-page bvec iterating Keith Busch
2023-11-21 5:01 ` Christoph Hellwig
2023-11-21 8:37 ` Ming Lei
2023-11-21 15:49 ` Keith Busch
2023-11-22 0:43 ` Ming Lei
2023-11-22 0:54 ` Keith Busch
2023-11-20 22:40 ` [PATCHv3 2/5] block: bio-integrity: directly map user buffers Keith Busch
2023-11-20 23:19 ` Jens Axboe
2023-11-21 5:04 ` Christoph Hellwig
2023-11-21 16:10 ` Anuj gupta
2023-11-20 22:40 ` [PATCHv3 3/5] nvme: use bio_integrity_map_user Keith Busch
2023-11-21 5:05 ` Christoph Hellwig
2023-11-20 22:40 ` [PATCHv3 4/5] iouring: remove IORING_URING_CMD_POLLED Keith Busch
2023-11-21 5:05 ` Christoph Hellwig
2023-11-20 22:40 ` [PATCHv3 5/5] io_uring: remove uring_cmd cookie Keith Busch
2023-11-21 5:05 ` 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