From: Damien Le Moal <dlemoal@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Carlos Maiolino <cem@kernel.org>
Cc: Jan Kara <jack@suse.cz>,
Filip Blagojevic <filip.blagojevic@wdc.com>,
Matthew Wilcox <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: update BDI {io,ra}_pages values based on the RT device limits
Date: Fri, 3 Jul 2026 07:25:32 +0900 [thread overview]
Message-ID: <faa6ca07-ddc4-4365-b1a5-8f02b32bfbbc@kernel.org> (raw)
In-Reply-To: <20260623142109.1838702-2-hch@lst.de>
On 6/23/26 23:21, Christoph Hellwig wrote:
> When using XFS with a main device on an SSD that stores metadata and a RT
> device to store data on a HDD, we fail to take the I/O sizes for the RT
> device into accounting, leading to up to 5% slower read performance when
> using an SSD for metadata vs storing data and metadata on the HDD.
>
> Fix this up by taking the RT settings into account. Note that this
> updates the BDI owned by the main device, and leaves those settings in
> place even when the file system is unmounted. This is a bit unexpected
> but not different from manual tuning through sysfs (although that is only
> possible for the ra_pages value).
>
> Reported-by: Filip Blagojevic <filip.blagojevic@wdc.com>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Until we have a better API to do this, given the performance improvements this
gives with HDDs, I am all for it.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-07-02 22:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 14:21 update BDI {io,ra}_pages values based on the RT device limits Christoph Hellwig
2026-06-23 14:21 ` [PATCH] xfs: " Christoph Hellwig
2026-07-02 22:25 ` Damien Le Moal [this message]
2026-06-24 10:40 ` Carlos Maiolino
2026-06-24 15:42 ` Christoph Hellwig
2026-06-24 12:26 ` Jan Kara
2026-06-24 13:49 ` Christoph Hellwig
2026-06-25 11:12 ` Jan Kara
2026-06-25 13:09 ` Christoph Hellwig
2026-06-29 12:46 ` 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=faa6ca07-ddc4-4365-b1a5-8f02b32bfbbc@kernel.org \
--to=dlemoal@kernel.org \
--cc=cem@kernel.org \
--cc=filip.blagojevic@wdc.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.