From: Christoph Hellwig <hch@infradead.org>
To: Boris Burkov <boris@bur.io>
Cc: linux-fsdevel@vger.kernel.org, lsf-pc@lists.linux-foundation.org,
linux-mm@kvack.org, linux-btrfs@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] Direct Reclaim and Filesystems
Date: Fri, 10 Apr 2026 00:08:10 -0700 [thread overview]
Message-ID: <adih2i15lagPQmGc@infradead.org> (raw)
In-Reply-To: <20260409210906.GA881465@zen.localdomain>
On Thu, Apr 09, 2026 at 02:09:06PM -0700, Boris Burkov wrote:
> - Reclaim freeing metadata and/or forcing metadata writeback [1][3][4]
> In btrfs, this results in redundant work fetching and writing btree nodes if
> it happens to hot nodes in the btree. Should we be trying to lock some of
> these nodes down from reclaim? If so, how many is appropriate/safe?
The solution to that is object based reclaim as in the xfs buffer
cache. That way you can set priorities on the nodes to keep them on
the LRU, or even pin things down much more easily.
When we last discussed this Josef didn't think it would work for btrfs
due to the amount of metadata, but I don't think that is a valid
argument.
prev parent reply other threads:[~2026-04-10 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 21:09 [LSF/MM/BPF TOPIC] Direct Reclaim and Filesystems Boris Burkov
2026-04-10 7:08 ` Christoph Hellwig [this message]
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=adih2i15lagPQmGc@infradead.org \
--to=hch@infradead.org \
--cc=boris@bur.io \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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