From: Brian Foster <bfoster@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>,
Dave Chinner <dchinner@redhat.com>,
linux-xfs@vger.kernel.org, "Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [PATCH 1/4] xfs: don't keep a reference for buffers on the LRU
Date: Wed, 18 Mar 2026 07:44:34 -0400 [thread overview]
Message-ID: <abqQIrwXzB_FiHFr@bfoster> (raw)
In-Reply-To: <20260317134110.1691097-2-hch@lst.de>
On Tue, Mar 17, 2026 at 02:40:52PM +0100, Christoph Hellwig wrote:
> Currently the buffer cache adds a reference to b_hold for buffers that
> are on the LRU. This seems to go all the way back and allows releasing
> buffers from the LRU using xfs_buf_rele. But it makes xfs_buf_rele
> really complicated in differs from how other LRUs are implemented in
> Linux.
>
> Switch to not having a reference for buffers in the LRU, and use a
> separate negative hold value to mark buffers as dead. This simplifies
> xfs_buf_rele, which now just deal with the last "real" reference,
> and prepares for using the lockref primitive.
>
> This also removes the b_lock protection for removing buffers from the
> buffer hash. This is the desired outcome because the rhashtable is
> fully internally synchronized, and previously the lock was mostly
> held out of ordering constrains in xfs_buf_rele_cached.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
> ---
> fs/xfs/xfs_buf.c | 139 ++++++++++++++++++-----------------------------
> fs/xfs/xfs_buf.h | 8 +--
> 2 files changed, 53 insertions(+), 94 deletions(-)
>
> diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c
> index d2f3c50d80e7..3cd37f082a69 100644
> --- a/fs/xfs/xfs_buf.c
> +++ b/fs/xfs/xfs_buf.c
...
> @@ -1610,11 +1564,12 @@ xfs_buftarg_isolate(
> struct list_head *dispose = arg;
>
> /*
> - * we are inverting the lru lock/bp->b_lock here, so use a trylock.
> - * If we fail to get the lock, just skip it.
> + * We are inverting the lru lock vs bp->b_lock order here, so use a
> + * trylock. If we fail to get the lock, just skip the buffer.
> */
> if (!spin_trylock(&bp->b_lock))
> return LRU_SKIP;
> +
> /*
> * Decrement the b_lru_ref count unless the value is already
> * zero. If the value is already zero, we need to reclaim the
> @@ -1624,8 +1579,18 @@ xfs_buftarg_isolate(
> spin_unlock(&bp->b_lock);
> return LRU_ROTATE;
> }
> +
(Trailing) Whitespace damage here ^, JFYI.
Otherwise LGTM. I like Dave's suggestion, but either way:
Reviewed-by: Brian Foster <bfoster@redhat.com>
> + /*
> + * If the buffer is in use, remove it from the LRU for now as we can't
> + * free it. It will be freed when the last reference drops.
> + */
> + if (bp->b_hold > 0) {
> + list_lru_isolate(lru, &bp->b_lru);
> + spin_unlock(&bp->b_lock);
> + return LRU_REMOVED;
> + }
>
> - bp->b_state |= XFS_BSTATE_DISPOSE;
> + bp->b_hold = -1;
> list_lru_isolate_move(lru, item, dispose);
> spin_unlock(&bp->b_lock);
> return LRU_REMOVED;
> @@ -1647,7 +1612,7 @@ xfs_buftarg_shrink_scan(
> struct xfs_buf *bp;
> bp = list_first_entry(&dispose, struct xfs_buf, b_lru);
> list_del_init(&bp->b_lru);
> - xfs_buf_rele(bp);
> + xfs_buf_destroy(bp);
> }
>
> return freed;
> diff --git a/fs/xfs/xfs_buf.h b/fs/xfs/xfs_buf.h
> index e25cd2a160f3..e7324d58bd96 100644
> --- a/fs/xfs/xfs_buf.h
> +++ b/fs/xfs/xfs_buf.h
> @@ -68,11 +68,6 @@ typedef unsigned int xfs_buf_flags_t;
> { XBF_INCORE, "INCORE" }, \
> { XBF_TRYLOCK, "TRYLOCK" }
>
> -/*
> - * Internal state flags.
> - */
> -#define XFS_BSTATE_DISPOSE (1 << 0) /* buffer being discarded */
> -
> struct xfs_buf_cache {
> struct rhashtable bc_hash;
> };
> @@ -159,7 +154,7 @@ struct xfs_buf {
>
> xfs_daddr_t b_rhash_key; /* buffer cache index */
> int b_length; /* size of buffer in BBs */
> - unsigned int b_hold; /* reference count */
> + int b_hold; /* reference count */
> atomic_t b_lru_ref; /* lru reclaim ref count */
> xfs_buf_flags_t b_flags; /* status flags */
> struct semaphore b_sema; /* semaphore for lockables */
> @@ -170,7 +165,6 @@ struct xfs_buf {
> */
> struct list_head b_lru; /* lru list */
> spinlock_t b_lock; /* internal state lock */
> - unsigned int b_state; /* internal state flags */
> wait_queue_head_t b_waiters; /* unpin waiters */
> struct list_head b_list;
> struct xfs_perag *b_pag;
> --
> 2.47.3
>
>
next prev parent reply other threads:[~2026-03-18 11:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 13:40 buffer cache simplification v5 Christoph Hellwig
2026-03-17 13:40 ` [PATCH 1/4] xfs: don't keep a reference for buffers on the LRU Christoph Hellwig
2026-03-17 21:33 ` Dave Chinner
2026-03-18 14:38 ` Christoph Hellwig
2026-03-18 11:44 ` Brian Foster [this message]
2026-03-17 13:40 ` [PATCH 2/4] xfs: use a lockref for the buffer reference count Christoph Hellwig
2026-03-17 21:53 ` Dave Chinner
2026-03-18 14:49 ` Christoph Hellwig
2026-03-17 13:40 ` [PATCH 3/4] xfs: switch (back) to a per-buftarg buffer hash Christoph Hellwig
2026-03-17 22:00 ` Dave Chinner
2026-03-18 12:14 ` Brian Foster
2026-03-17 13:40 ` [PATCH 4/4] xfs: don't decrement the buffer LRU count for in-use buffers Christoph Hellwig
2026-03-17 22:06 ` Dave Chinner
2026-03-18 11:47 ` Brian Foster
2026-03-18 11:45 ` Brian Foster
-- strict thread matches above, loose matches on Subject: below --
2026-03-23 7:50 buffer cache simplification v6 Christoph Hellwig
2026-03-23 7:50 ` [PATCH 1/4] xfs: don't keep a reference for buffers on the LRU 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=abqQIrwXzB_FiHFr@bfoster \
--to=bfoster@redhat.com \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@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