From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>,
Dave Chinner <dchinner@redhat.com>,
Brian Foster <bfoster@redhat.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/3] xfs: don't decrement the buffer LRU count for in-use buffers
Date: Mon, 16 Mar 2026 15:20:12 -0700 [thread overview]
Message-ID: <20260316222012.GA1770774@frogsfrogsfrogs> (raw)
In-Reply-To: <20260316154216.1598410-4-hch@lst.de>
On Mon, Mar 16, 2026 at 04:41:35PM +0100, Christoph Hellwig wrote:
> XFS buffers are added to the LRU when they are unused, but are only
> removed from the LRU lazily when the LRU list scan finds a used buffer.
> So far this only happen when the LRU counter hits 0, which is suboptimal
> as buffers that were added to the LRU, but are in use again still consume
> LRU scanning resources and are aged while actually in use.
>
> Fix this by checking for in-use buffers and removing the from the LRU
> before decrementing the LRU counter.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
That makes sense to me -- if someone holds the buffer, it's clearly not
cold and dead enough to get kicked out.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> fs/xfs/xfs_buf.c | 22 ++++++++++++----------
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c
> index c0a4d0a37f57..8ba9b74339a7 100644
> --- a/fs/xfs/xfs_buf.c
> +++ b/fs/xfs/xfs_buf.c
> @@ -1523,6 +1523,18 @@ xfs_buftarg_isolate(
> if (!spin_trylock(&bp->b_lockref.lock))
> return LRU_SKIP;
>
> + /*
> + * If the buffer is in use, remove it from the LRU for now. We can't
> + * free it while someone is using it, and we should also not count
> + * eviction passed for it, just as if it hadn't been added to the LRU
> + * yet.
> + */
> + if (bp->b_lockref.count > 0) {
> + list_lru_isolate(lru, &bp->b_lru);
> + spin_unlock(&bp->b_lockref.lock);
> + return LRU_REMOVED;
> + }
> +
> /*
> * Decrement the b_lru_ref count unless the value is already
> * zero. If the value is already zero, we need to reclaim the
> @@ -1533,16 +1545,6 @@ xfs_buftarg_isolate(
> return LRU_ROTATE;
> }
>
> - /*
> - * 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_lockref.count > 0) {
> - list_lru_isolate(lru, &bp->b_lru);
> - spin_unlock(&bp->b_lockref.lock);
> - return LRU_REMOVED;
> - }
> -
> lockref_mark_dead(&bp->b_lockref);
> list_lru_isolate_move(lru, item, dispose);
> spin_unlock(&bp->b_lockref.lock);
> --
> 2.47.3
>
>
next prev parent reply other threads:[~2026-03-16 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 15:41 buffer cache simplification v4 Christoph Hellwig
2026-03-16 15:41 ` [PATCH 1/3] xfs: use a lockref for the buffer reference count Christoph Hellwig
2026-03-16 15:41 ` [PATCH 2/3] xfs: switch (back) to a per-buftarg buffer hash Christoph Hellwig
2026-03-16 22:30 ` Darrick J. Wong
2026-03-16 15:41 ` [PATCH 3/3] xfs: don't decrement the buffer LRU count for in-use buffers Christoph Hellwig
2026-03-16 22:20 ` Darrick J. Wong [this message]
2026-03-17 12:13 ` buffer cache simplification v4 Brian Foster
2026-03-17 12:56 ` Christoph Hellwig
2026-03-17 13:36 ` Brian Foster
2026-03-17 13:39 ` 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=20260316222012.GA1770774@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--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