| Message ID | 20231128222752.1767344-1-kbusch@meta.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | block integrity: directly map user space addresses | expand |
Keith, > 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. Looks good to me. Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
From: Keith Busch <kbusch@kernel.org> 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(-)