From: Christoph Hellwig <hch@lst.de>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@lst.de>, Carlos Maiolino <cem@kernel.org>,
Filip Blagojevic <filip.blagojevic@wdc.com>,
Matthew Wilcox <willy@infradead.org>,
Damien Le Moal <dlemoal@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: update BDI {io,ra}_pages values based on the RT device limits
Date: Thu, 25 Jun 2026 15:09:46 +0200 [thread overview]
Message-ID: <20260625130946.GA23875@lst.de> (raw)
In-Reply-To: <ecyxpdw5jcqiw5lq26pi4af76tygoiqshj23hp7jkguvbn6o3z@bd3hnhglc4bo>
On Thu, Jun 25, 2026 at 01:12:05PM +0200, Jan Kara wrote:
> Hum, right. XFS users are used to tweak
> /sys/block/<dev>/queue/read_ahead_kb
> which would stop influencing anything. I guess that could indeed break some
> people's expectations.
Yeah.
> One more idea: We already cache bdi's ra_pages in struct file_ra_state on
> file open. It wouldn't be that hard to allow filesystem to override the
> values in its open method (currently it isn't possible only because
> file_ra_state_init() is called after ->open). For io_pages we currently
> always go to the bdi so we'd have to add it to struct file_ra_state.
It has to be called after ->open because ->open can change
file->f_mapping. Now we could require any instance changing it to also
call file_ra_state_init, but I think bloating every struct file with a
new field might not win a lot of friends. OTOH having a local copy
of ra_pages but not io_pages is really weird. But so is this whole
cascading set of indirections for the readahead parameters.
>
> Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
---end quoted text---
prev parent reply other threads:[~2026-06-25 13:09 UTC|newest]
Thread overview: 8+ 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-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 [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=20260625130946.GA23875@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=dlemoal@kernel.org \
--cc=filip.blagojevic@wdc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox