From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
Christian Brauner <brauner@kernel.org>,
Carlos Maiolino <cem@kernel.org>,
Tal Zussman <tz2294@columbia.edu>,
Anuj Gupta <anuj20.g@samsung.com>,
linux-block@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 20/22] xfs: add support for lazy direct read bounce buffering
Date: Thu, 23 Jul 2026 14:05:50 -0700 [thread overview]
Message-ID: <20260723210550.GJ2901224@frogsfrogsfrogs> (raw)
In-Reply-To: <20260723145000.116419-21-hch@lst.de>
On Thu, Jul 23, 2026 at 04:49:45PM +0200, Christoph Hellwig wrote:
> Currently direct I/O reads always bounce buffer the I/O to deal with
> the case where userspace is modifying the buffer in-flight while
> reading data into it.
>
> This is a very expensive countermeasure for something no sane application
> should do, so try to avoid it by reading without a bounce buffer first,
> and retrying the read on a checksum failure. This avoids the cost of
> bounce buffering for sanely behave applications. For the rare case of
> an application regularly modifying in-flight buffers, allow forcing the
> always bounce buffer behavior through sysfs. And now that we have that
> knob, allow disabling read-side bounce buffering entirely for those who
> live fast and dangerous.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Mostly looks fine, with only a couple of questions...
> ---
> fs/xfs/xfs_file.c | 4 +-
> fs/xfs/xfs_ioend.c | 99 ++++++++++++++++++++++++++++++++++++++++++++--
> fs/xfs/xfs_mount.h | 8 ++++
> fs/xfs/xfs_super.c | 1 +
> fs/xfs/xfs_sysfs.c | 65 ++++++++++++++++++++++++++++++
> fs/xfs/xfs_trace.h | 1 +
> 6 files changed, 172 insertions(+), 6 deletions(-)
>
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index d31a1dddcdc3..04301ab977a3 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -264,10 +264,8 @@ xfs_file_dio_read(
> ret = xfs_ilock_iocb(iocb, XFS_IOLOCK_SHARED);
> if (ret)
> return ret;
> - if (mapping_stable_writes(iocb->ki_filp->f_mapping)) {
> + if (mapping_stable_writes(iocb->ki_filp->f_mapping))
> dio_ops = &xfs_dio_read_bounce_ops;
> - dio_flags |= IOMAP_DIO_BOUNCE;
> - }
> ret = iomap_dio_rw(iocb, to, &xfs_read_iomap_ops, dio_ops, dio_flags,
> NULL, 0);
> xfs_iunlock(ip, XFS_IOLOCK_SHARED);
> diff --git a/fs/xfs/xfs_ioend.c b/fs/xfs/xfs_ioend.c
> index a095cf217863..94a81fb679ed 100644
> --- a/fs/xfs/xfs_ioend.c
> +++ b/fs/xfs/xfs_ioend.c
> @@ -1,6 +1,6 @@
> // SPDX-License-Identifier: GPL-2.0
> /*
> - * Copyright (c) 2016-2025 Christoph Hellwig.
> + * Copyright (c) 2016-2026 Christoph Hellwig.
> * All Rights Reserved.
> */
> #include "xfs_platform.h"
> @@ -18,15 +18,97 @@
> #include "xfs_ioend.h"
> #include <linux/bio-integrity.h>
>
> +static void
> +xfs_end_bio_bounced(
> + struct bio *bio)
> +{
> + iomap_finish_ioends(iomap_ioend_from_bio(bio),
> + blk_status_to_errno(bio->bi_status));
> +}
> +
> +static void
> +xfs_dio_bounce_end_io(
> + struct bio *bio)
> +{
> + struct iomap_ioend *ioend = iomap_ioend_from_bio(bio);
> + int error = blk_status_to_errno(bio->bi_status);
> + struct bio *orig_bio = bio->bi_private;
> +
> + if ((ioend->io_flags & IOMAP_IOEND_INTEGRITY) && !bio->bi_status)
> + error = iomap_ioend_integrity_verify(ioend);
> + iomap_bounce_read_end_io(ioend, orig_bio, error);
> +}
> +
> +static void
> +xfs_bounce_submit_ioend(
> + struct iomap_ioend *ioend)
> +{
> + if (ioend->io_flags & IOMAP_IOEND_INTEGRITY)
> + fs_bio_integrity_alloc(&ioend->io_bio);
> + ioend->io_bio.bi_end_io = xfs_dio_bounce_end_io;
> + bio_set_flag(&ioend->io_bio, BIO_COMPLETE_IN_TASK);
> + submit_bio(&ioend->io_bio);
> +}
> +
> +static void
> +xfs_read_bounce_and_resubmit(
> + struct iomap_ioend *ioend)
> +{
> + struct bio *bio = &ioend->io_bio;
> +
> + trace_xfs_bounce_reread(XFS_I(ioend->io_inode), ioend->io_offset,
> + ioend->io_size);
> +
> + /*
> + * Free the bio integrity data for the original bio, as we'll allocate
> + * ons for each sub-I/O, which could deadlock if we keep the original
> + * one around.
> + */
> + if (ioend->io_flags & IOMAP_IOEND_INTEGRITY)
> + fs_bio_integrity_free(bio);
> +
> + /*
> + * Reset the remaining count, iter and bdev as we submit the bio to the
> + * block layer again and we need a clean slate. Switch to and end_io
> + * handler that simply complets the ioend, as all the verification is
> + * done by the end_I/O handlers for the clone bio(s).
> + */
> + atomic_set(&bio->__bi_remaining, 1);
> + bio->bi_iter = (struct bvec_iter) {
> + .bi_sector = ioend->io_sector,
> + .bi_size = ioend->io_size,
> + .bi_bvec_done = ioend->io_bvec_offset,
> + };
> + bio->bi_bdev = xfs_inode_buftarg(XFS_I(ioend->io_inode))->bt_bdev;
> + bio->bi_end_io = xfs_end_bio_bounced;
> + iomap_bounce_read(ioend, bdev_logical_block_size(bio->bi_bdev),
> + xfs_bounce_submit_ioend);
> +}
> +
> static void
> xfs_end_io_read(
> struct bio *bio)
> {
> struct iomap_ioend *ioend = iomap_ioend_from_bio(bio);
> + struct xfs_inode *ip = XFS_I(ioend->io_inode);
> + struct xfs_mount *mp = ip->i_mount;
> int error = blk_status_to_errno(bio->bi_status);
>
> - if (!error && (ioend->io_flags & IOMAP_IOEND_INTEGRITY))
> + if (!error && (ioend->io_flags & IOMAP_IOEND_INTEGRITY)) {
> error = iomap_ioend_integrity_verify(ioend);
> + if ((ioend->io_flags & IOMAP_IOEND_DIRECT) &&
> + READ_ONCE(mp->m_read_bounce) == XFS_READ_BOUNCE_LAZY) {
> + /*
> + * We only really need to retry for guard tag errors,
> + * but right now we can't distinguish them from other
> + * (i.e, reftag) errors.
> + */
> + if (error) {
> + xfs_read_bounce_and_resubmit(ioend);
Ahah, yes we are being mean and making userspace wait for a slow bounce
buffer workaround if they mess with us.
> + return;
> + }
> + }
> + }
>
> iomap_finish_ioends(ioend, error);
> }
> @@ -38,7 +120,18 @@ xfs_ioend_submit_read(
> loff_t file_offset,
> u16 ioend_flags)
> {
> - iomap_init_ioend(inode, bio, file_offset, ioend_flags);
> + struct xfs_inode *ip = XFS_I(inode);
> + struct xfs_mount *mp = ip->i_mount;
> + struct iomap_ioend *ioend;
> +
> + ioend = iomap_init_ioend(inode, bio, file_offset, ioend_flags);
> + if ((ioend_flags & IOMAP_IOEND_DIRECT) &&
> + READ_ONCE(mp->m_read_bounce) == XFS_READ_BOUNCE_ALWAYS) {
> + iomap_bounce_read(ioend, bdev_logical_block_size(bio->bi_bdev),
> + xfs_bounce_submit_ioend);
> + return;
> + }
> +
> if (ioend_flags & IOMAP_IOEND_INTEGRITY)
> fs_bio_integrity_alloc(bio);
> bio->bi_end_io = xfs_end_io_read;
> diff --git a/fs/xfs/xfs_mount.h b/fs/xfs/xfs_mount.h
> index 66a02d1b9ad7..6f8119bd959c 100644
> --- a/fs/xfs/xfs_mount.h
> +++ b/fs/xfs/xfs_mount.h
> @@ -142,6 +142,12 @@ struct xfs_freecounter {
> uint64_t res_saved;
> };
>
> +enum xfs_read_bounce {
> + XFS_READ_BOUNCE_NEVER,
> + XFS_READ_BOUNCE_ALWAYS,
> + XFS_READ_BOUNCE_LAZY,
> +};
> +
> /*
> * The struct xfsmount layout is optimised to separate read-mostly variables
> * from variables that are frequently modified. We put the read-mostly variables
> @@ -177,6 +183,7 @@ typedef struct xfs_mount {
> struct workqueue_struct *m_sync_workqueue;
> struct workqueue_struct *m_blockgc_wq;
> struct workqueue_struct *m_inodegc_wq;
> + enum xfs_read_bounce m_read_bounce;
>
> int m_bsize; /* fs logical block size */
> uint8_t m_blkbit_log; /* blocklog + NBBY */
> @@ -291,6 +298,7 @@ typedef struct xfs_mount {
> struct xfs_zone_info *m_zone_info; /* zone allocator information */
> struct dentry *m_debugfs; /* debugfs parent */
> struct xfs_kobj m_kobj;
> + struct xfs_kobj m_csum_kobj;
> struct xfs_kobj m_error_kobj;
> struct xfs_kobj m_error_meta_kobj;
> struct xfs_error_cfg m_error_cfg[XFS_ERR_CLASS_MAX][XFS_ERR_ERRNO_MAX];
> diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
> index 8531d526fc44..7c8424185e06 100644
> --- a/fs/xfs/xfs_super.c
> +++ b/fs/xfs/xfs_super.c
> @@ -2270,6 +2270,7 @@ xfs_init_fs_context(
> mp->m_logbufs = -1;
> mp->m_logbsize = -1;
> mp->m_allocsize_log = 16; /* 64k */
> + mp->m_read_bounce = XFS_READ_BOUNCE_LAZY;
>
> xfs_hooks_init(&mp->m_dir_update_hooks);
>
> diff --git a/fs/xfs/xfs_sysfs.c b/fs/xfs/xfs_sysfs.c
> index b62712187324..1e44bb8b30e8 100644
> --- a/fs/xfs/xfs_sysfs.c
> +++ b/fs/xfs/xfs_sysfs.c
> @@ -392,6 +392,63 @@ const struct kobj_type xfs_stats_ktype = {
> .default_groups = xfs_stats_groups,
> };
>
> +static inline struct xfs_mount *csum_to_mp(struct kobject *kobj)
> +{
> + return container_of(to_kobj(kobj), struct xfs_mount, m_csum_kobj);
> +}
> +
> +static ssize_t
> +read_bounce_show(
> + struct kobject *kobj,
> + char *buf)
> +{
> + struct xfs_mount *mp = csum_to_mp(kobj);
> +
> + switch (READ_ONCE(mp->m_read_bounce)) {
> + case XFS_READ_BOUNCE_NEVER:
> + return sysfs_emit(buf, "never\n");
> + case XFS_READ_BOUNCE_ALWAYS:
> + return sysfs_emit(buf, "always\n");
> + case XFS_READ_BOUNCE_LAZY:
> + return sysfs_emit(buf, "lazy\n");
> + default:
> + return sysfs_emit(buf, "invalid\n");
> + }
> +}
> +
> +static ssize_t
> +read_bounce_store(
> + struct kobject *kobj,
> + const char *buf,
> + size_t count)
> +{
> + struct xfs_mount *mp = csum_to_mp(kobj);
> +
> + if (!strcmp(buf, "never"))
> + WRITE_ONCE(mp->m_read_bounce, XFS_READ_BOUNCE_NEVER);
> + else if (!strcmp(buf, "always"))
> + WRITE_ONCE(mp->m_read_bounce, XFS_READ_BOUNCE_ALWAYS);
> + else if (!strcmp(buf, "lazy"))
> + WRITE_ONCE(mp->m_read_bounce, XFS_READ_BOUNCE_LAZY);
> + else
> + return -EINVAL;
> +
> + return count;
> +}
> +XFS_SYSFS_ATTR_RW(read_bounce);
> +
> +static struct attribute *xfs_csum_attrs[] = {
> + ATTR_LIST(read_bounce),
> + NULL,
> +};
> +ATTRIBUTE_GROUPS(xfs_csum);
> +
> +static const struct kobj_type xfs_csum_ktype = {
> + .release = xfs_sysfs_release,
> + .sysfs_ops = &xfs_sysfs_ops,
> + .default_groups = xfs_csum_groups,
> +};
> +
> /* xlog */
>
> static inline struct xlog *
> @@ -837,6 +894,12 @@ xfs_mount_sysfs_init(
> if (error)
> goto out_remove_error_dir;
>
> + /* .../xfs/<dev>/csum/ */
> + error = xfs_sysfs_init(&mp->m_csum_kobj, &xfs_csum_ktype,
> + &mp->m_kobj, "csum");
> + if (error)
> + goto out_remove_error_dir;
/me wonders if this is a debugging knob and therefore should go in
debugfs? Or is there a solid usecase for normal sysadmins to be able to
control this?
--D
> +
> return 0;
>
> out_remove_error_dir:
> @@ -855,6 +918,8 @@ xfs_mount_sysfs_del(
> struct xfs_error_cfg *cfg;
> int i, j;
>
> + xfs_sysfs_del(&mp->m_csum_kobj);
> +
> for (i = 0; i < XFS_ERR_CLASS_MAX; i++) {
> for (j = 0; j < XFS_ERR_ERRNO_MAX; j++) {
> cfg = &mp->m_error_cfg[i][j];
> diff --git a/fs/xfs/xfs_trace.h b/fs/xfs/xfs_trace.h
> index aeb89ac53bf1..af44551fd305 100644
> --- a/fs/xfs/xfs_trace.h
> +++ b/fs/xfs/xfs_trace.h
> @@ -1896,6 +1896,7 @@ DEFINE_SIMPLE_IO_EVENT(xfs_zero_eof);
> DEFINE_SIMPLE_IO_EVENT(xfs_end_io_direct_write);
> DEFINE_SIMPLE_IO_EVENT(xfs_file_splice_read);
> DEFINE_SIMPLE_IO_EVENT(xfs_zoned_map_blocks);
> +DEFINE_SIMPLE_IO_EVENT(xfs_bounce_reread);
>
> DECLARE_EVENT_CLASS(xfs_itrunc_class,
> TP_PROTO(struct xfs_inode *ip, xfs_fsize_t new_size),
> --
> 2.53.0
>
>
next prev parent reply other threads:[~2026-07-23 21:05 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 14:49 lazy bounce buffering for checksummed reads Christoph Hellwig
2026-07-23 14:49 ` [PATCH 01/22] iomap: add a separate bio_set for iomap_split_ioend Christoph Hellwig
2026-07-23 16:49 ` Darrick J. Wong
2026-07-23 14:49 ` [PATCH 02/22] block: remove bip_should_check Christoph Hellwig
2026-07-23 14:49 ` [PATCH 03/22] block: lift BIP_CHECK_FLAGS to include/linux/bio-integrity.h Christoph Hellwig
2026-07-23 14:49 ` [PATCH 04/22] block: handle nogenerate/noverify properly in fs-integrity Christoph Hellwig
2026-07-23 17:05 ` Anuj gupta
2026-07-23 14:49 ` [PATCH 05/22] iomap: don't free integrity payload that doesn't exist Christoph Hellwig
2026-07-23 16:55 ` Darrick J. Wong
2026-07-23 14:49 ` [PATCH 06/22] block,iomap: fix protection information verification with initial bvec offset Christoph Hellwig
2026-07-23 14:49 ` [PATCH 07/22] block: add task-context bio completion infrastructure Christoph Hellwig
2026-07-23 14:49 ` [PATCH 08/22] block: don't delay bio task completions Christoph Hellwig
2026-07-23 14:49 ` [PATCH 09/22] block: split bio_iov_iter_bounce_write Christoph Hellwig
2026-07-23 14:49 ` [PATCH 10/22] block: export fs_bio_integrity_{alloc,free} Christoph Hellwig
2026-07-23 14:49 ` [PATCH 11/22] block: don't include blk-integrity.h in bdev.c Christoph Hellwig
2026-07-23 14:49 ` [PATCH 12/22] iomap: better read bounce buffering support Christoph Hellwig
2026-07-23 21:10 ` Darrick J. Wong
2026-07-23 14:49 ` [PATCH 13/22] iomap: add a iomap_ioend_flags helper Christoph Hellwig
2026-07-23 20:52 ` Darrick J. Wong
2026-07-23 14:49 ` [PATCH 14/22] iomap: add a IOMAP_IOEND_INTEGRITY flag Christoph Hellwig
2026-07-23 20:53 ` Darrick J. Wong
2026-07-23 14:49 ` [PATCH 15/22] iomap,xfs: move T10 PI handling for direct I/O into ->submit_io Christoph Hellwig
2026-07-23 20:55 ` Darrick J. Wong
2026-07-23 14:49 ` [PATCH 16/22] xfs: move PI generation into xfs_zone_alloc_and_submit Christoph Hellwig
2026-07-23 20:55 ` Darrick J. Wong
2026-07-23 14:49 ` [PATCH 17/22] xfs: split ioend handling into a separate source file Christoph Hellwig
2026-07-23 20:55 ` Darrick J. Wong
2026-07-23 14:49 ` [PATCH 18/22] xfs: use BIO_COMPLETE_IN_TASK for bounce buffered read I/Os Christoph Hellwig
2026-07-23 15:58 ` Andrey Albershteyn
2026-07-23 20:58 ` Darrick J. Wong
2026-07-23 14:49 ` [PATCH 19/22] iomap,xfs: move integrity verification to the file system Christoph Hellwig
2026-07-23 21:02 ` Darrick J. Wong
2026-07-23 14:49 ` [PATCH 20/22] xfs: add support for lazy direct read bounce buffering Christoph Hellwig
2026-07-23 21:05 ` Darrick J. Wong [this message]
2026-07-23 14:49 ` [PATCH 21/22] xfs: add error injection for lazy " Christoph Hellwig
2026-07-23 21:06 ` Darrick J. Wong
2026-07-23 14:49 ` [PATCH 22/22] xfs: log a message at mount time when using integrity protection Christoph Hellwig
2026-07-23 21:07 ` Darrick J. Wong
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 \
--in-reply-to=20260723210550.GJ2901224@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tz2294@columbia.edu \
/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