From: "Alexander V. Buev" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>, Jens Axboe <[email protected]>,
Christoph Hellwig <[email protected]>,
"Martin K . Petersen" <[email protected]>,
Pavel Begunkov <[email protected]>,
Chaitanya Kulkarni <[email protected]>,
Mikhail Malygin <[email protected]>, <[email protected]>,
"Alexander V. Buev" <[email protected]>
Subject: [PATCH v2 0/3] implement direct IO with integrity
Date: Thu, 10 Feb 2022 16:08:22 +0300 [thread overview]
Message-ID: <[email protected]> (raw)
This series of patches makes possible to do direct block IO
with integrity payload using io uring kernel interface.
Userspace app can utilize new READV_PI/WRITEV_PI operation with a new
fields in sqe struct (pi_addr/pi_len) to provide iovec's with
integrity data.
Changes since v1:
- switch to using separated io uring op codes and additional
sqe fields (instead of sqe flag)
- ability to process multiple iovecs
- use unused space in bio to pin user pages
Alexander V. Buev (3):
block: bio-integrity: add PI iovec to bio
block: io_uring: add READV_PI/WRITEV_PI operations
block: fops: handle IOCB_USE_PI in direct IO
block/bio-integrity.c | 151 +++++++++++++++++++++++
block/fops.c | 62 ++++++++++
fs/io_uring.c | 209 ++++++++++++++++++++++++++++++++
include/linux/bio.h | 8 ++
include/linux/fs.h | 2 +
include/trace/events/io_uring.h | 17 +--
include/uapi/linux/io_uring.h | 6 +-
include/uapi/linux/uio.h | 3 +-
8 files changed, 449 insertions(+), 9 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-10 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 13:08 Alexander V. Buev [this message]
2022-02-10 13:08 ` [PATCH v2 1/3] block: bio-integrity: add PI iovec to bio Alexander V. Buev
2022-02-10 17:49 ` Chaitanya Kulkarni
2022-02-10 13:08 ` [PATCH v2 2/3] block: io_uring: add READV_PI/WRITEV_PI operations Alexander V. Buev
2022-02-10 15:39 ` Jens Axboe
2022-02-10 19:03 ` Alexander V. Buev
2022-02-10 19:07 ` Jens Axboe
2022-02-11 9:39 ` Alexander V. Buev
2022-02-10 13:08 ` [PATCH v2 3/3] block: fops: handle IOCB_USE_PI in direct IO Alexander V. Buev
2022-02-10 17:53 ` Chaitanya Kulkarni
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