Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 12/12] xfs: add lockless xfs_buf_readahead_map fast path
Date: Fri, 24 Jul 2026 10:03:16 -0700	[thread overview]
Message-ID: <20260724170316.GZ2901224@frogsfrogsfrogs> (raw)
In-Reply-To: <20260715145147.95654-13-hch@lst.de>

On Wed, Jul 15, 2026 at 04:51:05PM +0200, Christoph Hellwig wrote:
> Readahead currently always locks the buffer, which can cause contention
> with actual users of the buffer.  Add a fast path without taking any
> locks if the buffer is uptodate and not stale.

So we're trying to cut down on b_sema contention for detecting the case
where the buffer is already uptodate?  And I guess the idea here is that
if you had per-fsblock filesystem metadata, you'd want to be able to
readahead that metadata into memory during setup for file IO without
so much locking?

Sounds reasonable to me...
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D


> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  fs/xfs/xfs_buf.c | 16 +++++++++++++---
>  1 file changed, 13 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c
> index f5701f74061f..2e498e9e05e9 100644
> --- a/fs/xfs/xfs_buf.c
> +++ b/fs/xfs/xfs_buf.c
> @@ -756,13 +756,23 @@ xfs_buf_readahead_map(
>  
>  	if (xfs_find_get_buf(target, map, nmaps, flags, &bp))
>  		return;
> -	if (xfs_buf_find_lock(bp, XBF_TRYLOCK))
> +
> +	/*
> +	 * Do a lockless fast path check for a valid uptodate buffer and avoid
> +	 * locking entirely in this case.
> +	 */
> +	if ((READ_ONCE(bp->b_flags) & (XBF_DONE | XBF_STALE)) == XBF_DONE)
>  		goto out_rele;
>  
> -	trace_xfs_buf_readahead(bp, 0, _RET_IP_);
> -	if (bp->b_flags & XBF_DONE)
> +	/* Otherwise lock the buffer to stabilize the state */
> +	if (!xfs_buf_trylock(bp))
> +		goto out_rele;
> +
> +	/* Let the actual reader deal with stale buffers. */
> +	if (bp->b_flags & (XBF_STALE | XBF_DONE))
>  		goto out_unlock;
>  
> +	trace_xfs_buf_readahead(bp, 0, _RET_IP_);
>  	XFS_STATS_INC(target->bt_mount, xb_get_read);
>  	bp->b_ops = ops;
>  	xfs_buf_clear_flags(bp, XBF_WRITE | XBF_DONE);
> -- 
> 2.53.0
> 
> 

  reply	other threads:[~2026-07-24 17:03 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 14:50 misc buffer cache improvements Christoph Hellwig
2026-07-15 14:50 ` [PATCH 01/12] xfs: don't get a pag reference in xfs_buf_get_map Christoph Hellwig
2026-07-24 16:32   ` Darrick J. Wong
2026-07-15 14:50 ` [PATCH 02/12] xfs: consolidate buffer locking " Christoph Hellwig
2026-07-16 13:12   ` Brian Foster
2026-07-17  8:59     ` Christoph Hellwig
2026-07-17 14:13       ` Brian Foster
2026-07-20  7:59         ` Christoph Hellwig
2026-07-24 16:42           ` Darrick J. Wong
2026-07-28  4:38             ` Christoph Hellwig
2026-07-15 14:50 ` [PATCH 03/12] xfs: split out a lower-level xfs_buf_get_map helper from xfs_find_get_buf Christoph Hellwig
2026-07-24 16:44   ` Darrick J. Wong
2026-07-28  4:39     ` Christoph Hellwig
2026-07-15 14:50 ` [PATCH 04/12] xfs: remove spurious XBF_DONE clearing on readahead validation failure Christoph Hellwig
2026-07-24 16:45   ` Darrick J. Wong
2026-07-15 14:50 ` [PATCH 05/12] xfs: remove _XBF_LOGRECOVERY Christoph Hellwig
2026-07-24 16:49   ` Darrick J. Wong
2026-07-28  4:39     ` Christoph Hellwig
2026-07-15 14:50 ` [PATCH 06/12] xfs: hide b_flags manipulation from code outside of xfs_buf.c Christoph Hellwig
2026-07-24 16:49   ` Darrick J. Wong
2026-07-15 14:51 ` [PATCH 07/12] xfs: use WRITE_ONCE to update b_flags Christoph Hellwig
2026-07-24 16:53   ` Darrick J. Wong
2026-07-28  4:40     ` Christoph Hellwig
2026-07-15 14:51 ` [PATCH 08/12] xfs: don't reverify buffers in xfs_buf_readahead_map Christoph Hellwig
2026-07-24 16:56   ` Darrick J. Wong
2026-07-15 14:51 ` [PATCH 09/12] xfs: use goto based error unwinding in xfs_buf_read_map Christoph Hellwig
2026-07-24 16:57   ` Darrick J. Wong
2026-07-15 14:51 ` [PATCH 10/12] xfs: merge xfs_buf_reverify into xfs_buf_read_map Christoph Hellwig
2026-07-17 14:13   ` Brian Foster
2026-07-24 16:58   ` Darrick J. Wong
2026-07-15 14:51 ` [PATCH 11/12] xfs: move buffer locking out of xfs_find_get_buf Christoph Hellwig
2026-07-24 16:59   ` Darrick J. Wong
2026-07-15 14:51 ` [PATCH 12/12] xfs: add lockless xfs_buf_readahead_map fast path Christoph Hellwig
2026-07-24 17:03   ` Darrick J. Wong [this message]
2026-07-28  4:41     ` Christoph Hellwig
2026-08-10 11:55 ` misc buffer cache improvements Carlos Maiolino
  -- strict thread matches above, loose matches on Subject: below --
2026-07-28  8:11 misc buffer cache improvements v2 Christoph Hellwig
2026-07-28  8:11 ` [PATCH 12/12] xfs: add lockless xfs_buf_readahead_map fast path 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 \
    --in-reply-to=20260724170316.GZ2901224@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    /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