Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
	Damien Le Moal <dlemoal@kernel.org>, 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: Tue, 21 Jul 2026 08:18:52 -0700	[thread overview]
Message-ID: <20260721151852.GA7358@frogsfrogsfrogs> (raw)
In-Reply-To: <al86SnXSDqQ0sKkR@nidhogg.toxiclabs.cc>

On Tue, Jul 21, 2026 at 11:23:29AM +0200, Carlos Maiolino wrote:
> On Tue, Jul 21, 2026 at 06:30:11AM +0200, Christoph Hellwig wrote:
> > On Tue, Jul 21, 2026 at 08:07:40AM +0900, Damien Le Moal wrote:
> > > > + * Update the BDI values to the max of the data and RT device to cover our
> > > 
> > > s/data/main ?
> > > I am still confused about the proper name for the device holding metadata :)
> > > 
> > > Other than this, this looks OK to me.
> > 
> > Historically the main device is called the data device, which is
> > also reflected in all kinds of field naming.  But yes, it is confusing
> > especially for zoned xfs setups.  Maybe I should do a little global
> > naming sweep..
> > 
> > 
> 
> +1, please keep /data/ here, this makes much more sense in xfs lingo...
> Perhaps we should start naming them to something like ndata (for normal
> data) and zdata for zoned data, but that's talk for another thread.

I've been trying to be consistent at calling them the 'datadev' and
'rtdev' (no spaces) so it's more obvious that I'm using a jargon.  But
'rt' makes no sense these days and I never did come up with a good
retcon for it though.

"RelaTive"?  Because the rtdev is "related" to the datadev by metadata?

:D

--D

  reply	other threads:[~2026-07-21 15:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 14:08 update BDI {io,ra}_pages values based on the RT device limits v2 Christoph Hellwig
2026-07-20 14:08 ` [PATCH] xfs: update BDI {io,ra}_pages values based on the RT device limits Christoph Hellwig
2026-07-20 23:07   ` Damien Le Moal
2026-07-21  4:30     ` Christoph Hellwig
2026-07-21  9:23       ` Carlos Maiolino
2026-07-21 15:18         ` Darrick J. Wong [this message]
2026-07-21  9:24   ` Carlos Maiolino
2026-07-21 10:44   ` Carlos Maiolino
  -- strict thread matches above, loose matches on Subject: below --
2026-06-23 14:21 Christoph Hellwig
2026-06-23 14:21 ` [PATCH] xfs: " Christoph Hellwig
2026-07-02 22:25   ` Damien Le Moal
2026-07-20  9:02   ` Carlos Maiolino
2026-07-20  9:11     ` Christoph Hellwig
2026-07-20  9:38       ` Carlos Maiolino

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=20260721151852.GA7358@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=dlemoal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox