From: Mark Harmstone <[email protected]>
To: <[email protected]>, <[email protected]>
Cc: Mark Harmstone <[email protected]>
Subject: [PATCH 0/6] btrfs: add io_uring for encoded reads
Date: Fri, 23 Aug 2024 17:27:42 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
This patch series adds io_uring support for btrfs encoded reads,
complementing the ioctl we already have. The first few patches refactor
the ioctl code so that the bio wait is moved to the outer function, and
so that we can share as much code as possible between the two
interfaces.
Mark Harmstone (6):
btrfs: remove iocb from btrfs_encoded_read
btrfs: store encoded read state in struct btrfs_encoded_read_private
btrfs: add btrfs_encoded_read_finish
btrfs: add btrfs_prepare_encoded_read
btrfs: move wait out of btrfs_encoded_read
btrfs: add io_uring interface for encoded reads
fs/btrfs/btrfs_inode.h | 23 +++-
fs/btrfs/file.c | 1 +
fs/btrfs/inode.c | 292 ++++++++++++++++++++++++-----------------
fs/btrfs/ioctl.c | 194 +++++++++++++++++++--------
fs/btrfs/ioctl.h | 3 +
5 files changed, 337 insertions(+), 176 deletions(-)
--
2.44.2
next reply other threads:[~2024-08-23 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 16:27 Mark Harmstone [this message]
2024-08-23 16:27 ` [PATCH 1/6] btrfs: remove iocb from btrfs_encoded_read Mark Harmstone
2024-08-27 1:12 ` David Sterba
2024-08-23 16:27 ` [PATCH 2/6] btrfs: store encoded read state in struct btrfs_encoded_read_private Mark Harmstone
2024-08-26 15:22 ` David Sterba
2024-08-27 1:03 ` David Sterba
2024-09-06 15:19 ` Pavel Begunkov
2024-08-23 16:27 ` [PATCH 3/6] btrfs: add btrfs_encoded_read_finish Mark Harmstone
2024-08-23 16:27 ` [PATCH 4/6] btrfs: add btrfs_prepare_encoded_read Mark Harmstone
2024-08-23 16:27 ` [PATCH 5/6] btrfs: move wait out of btrfs_encoded_read Mark Harmstone
2024-09-06 15:11 ` Pavel Begunkov
2024-08-23 16:27 ` [PATCH 6/6] btrfs: add io_uring interface for encoded reads Mark Harmstone
2024-09-06 14:41 ` Pavel Begunkov
2024-09-06 15:33 ` Pavel Begunkov
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] \
/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