From: Damien Le Moal <dlemoal@kernel.org>
To: Christoph Hellwig <hch@lst.de>, cem@kernel.org
Cc: hans.holmberg@wdc.com, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: cache open zone in inode->i_private
Date: Sat, 18 Oct 2025 13:17:18 +0900 [thread overview]
Message-ID: <677e4465-fa8d-4363-be07-523c4b6f7d2a@kernel.org> (raw)
In-Reply-To: <20251017035607.652393-1-hch@lst.de>
On 10/17/25 12:55, Christoph Hellwig wrote:
> The MRU cache for open zones is unfortunately still not ideal, as it can
> time out pretty easily when doing heavy I/O to hard disks using up most
> or all open zones. One option would be to just increase the timeout,
> but while looking into that I realized we're just better off caching it
> indefinitely as there is no real downside to that once we don't hold a
> reference to the cache open zone.
>
> So switch the open zone to RCU freeing, and then stash the last used
> open zone into inode->i_private. This helps to significantly reduce
> fragmentation by keeping I/O localized to zones for workloads that
> write using many open files to HDD.
>
> Fixes: 4e4d52075577 ("xfs: add the zoned space allocator")
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
Tested-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-10-18 4:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 3:55 [PATCH v2] xfs: cache open zone in inode->i_private Christoph Hellwig
2025-10-18 4:17 ` Damien Le Moal [this message]
2025-10-20 8:17 ` Hans Holmberg
2025-10-21 9:37 ` Carlos Maiolino
-- strict thread matches above, loose matches on Subject: below --
2025-10-17 3:51 Christoph Hellwig
2025-10-17 5:27 ` 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=677e4465-fa8d-4363-be07-523c4b6f7d2a@kernel.org \
--to=dlemoal@kernel.org \
--cc=cem@kernel.org \
--cc=hans.holmberg@wdc.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;
as well as URLs for NNTP newsgroup(s).