From: Carlos Maiolino <cem@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Niklas Cassel <cassel@kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
Hans Holmberg <hans.holmberg@wdc.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/2] xfs: add additional zoned sysfs attributes
Date: Wed, 22 Apr 2026 09:17:59 +0200 [thread overview]
Message-ID: <aeh1_o_12LSI71TI@nidhogg.toxiclabs.cc> (raw)
In-Reply-To: <20260422060228.GB5391@lst.de>
On Wed, Apr 22, 2026 at 08:02:28AM +0200, Christoph Hellwig wrote:
> On Mon, Apr 20, 2026 at 03:50:12PM +0200, Niklas Cassel wrote:
> > Hello all,
> >
> > This series adds:
> > /sys/fs/xfs/<dev>/zoned/nr_free_zones
> > and
> > /sys/fs/xfs/<dev>/zoned/zonegc_required
> >
> > These values are already available in /proc/<pid>/mountstats, however,
> > mountstats will unconditionally print the stats for all mounted zoned XFS
> > filesystems.
> >
> > Making the same information in /sys/fs/xfs/<dev>/zoned/ makes it easier
> > for monitoring tools software to read the values for a specific filesystem.
>
> What monitoring tools software are you aiming for?
Zonar perhaps?
>
>
prev parent reply other threads:[~2026-04-22 7:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 13:50 [PATCH 0/2] xfs: add additional zoned sysfs attributes Niklas Cassel
2026-04-20 13:50 ` [PATCH 1/2] xfs: expose the number of free zones in sysfs Niklas Cassel
2026-04-20 15:39 ` Damien Le Moal
2026-04-22 6:03 ` Christoph Hellwig
2026-04-20 13:50 ` [PATCH 2/2] xfs: expose the current zonegc required status " Niklas Cassel
2026-04-20 15:47 ` Damien Le Moal
2026-04-20 16:09 ` Niklas Cassel
2026-04-22 6:04 ` Christoph Hellwig
2026-04-22 6:02 ` [PATCH 0/2] xfs: add additional zoned sysfs attributes Christoph Hellwig
2026-04-22 7:17 ` Carlos Maiolino [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=aeh1_o_12LSI71TI@nidhogg.toxiclabs.cc \
--to=cem@kernel.org \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--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