From: Christoph Hellwig <hch@lst.de>
To: Niklas Cassel <cassel@kernel.org>
Cc: Carlos Maiolino <cem@kernel.org>, Christoph Hellwig <hch@lst.de>,
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 2/2] xfs: expose the current zonegc required status in sysfs
Date: Wed, 22 Apr 2026 08:04:17 +0200 [thread overview]
Message-ID: <20260422060417.GD5391@lst.de> (raw)
In-Reply-To: <20260420135011.624587-6-cassel@kernel.org>
On Mon, Apr 20, 2026 at 03:50:14PM +0200, Niklas Cassel wrote:
> The current zonegc required status is currently available in
> /proc/<pid>/mountstats (which contains stats for all mounted zoned XFS
> filesystems), under "RT GC required:".
>
> Add a sysfs attribute /sys/fs/xfs/<dev>/zoned/zonegc_required for the same.
> This makes it trivial for monitoring software to read the value, for a
> specific filesystem, without any complex parsing.
GC needed is a very complex internal condition, and I don't think
exposing the current value as a stable ABI is a good idea.
What are you trying to do with this information?
next prev parent reply other threads:[~2026-04-22 6:04 UTC|newest]
Thread overview: 13+ 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-22 10:29 ` Niklas Cassel
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 [this message]
2026-04-22 10:31 ` Niklas Cassel
2026-04-22 6:02 ` [PATCH 0/2] xfs: add additional zoned sysfs attributes Christoph Hellwig
2026-04-22 7:17 ` Carlos Maiolino
2026-04-22 9:53 ` Niklas Cassel
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=20260422060417.GD5391@lst.de \
--to=hch@lst.de \
--cc=cassel@kernel.org \
--cc=cem@kernel.org \
--cc=dlemoal@kernel.org \
--cc=hans.holmberg@wdc.com \
--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