All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Niklas Cassel <cassel@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Carlos Maiolino <cem@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 2/2] xfs: expose the current zonegc required status in sysfs
Date: Thu, 23 Apr 2026 07:12:44 +0200	[thread overview]
Message-ID: <20260423051244.GB27929@lst.de> (raw)
In-Reply-To: <aeijmOd6zHDQeA7x@ryzen>

On Wed, Apr 22, 2026 at 12:31:52PM +0200, Niklas Cassel wrote:
> Or perhaps I am missing something here, and for some reason, unlike a sysfs
> attribute, the information exposed in /proc/<pid>/mountstats is not considered
> a stable ABI ?
> 
> 
> That said, if you prefer 2) or 3) over 1) for exposing zonegc_required,
> please tell me which you prefer, and I can send a V2 with that.

I'd prefer not adding another API for querying this detail.  Especially
no a fairly heavy weight one.

  reply	other threads:[~2026-04-23  5:12 UTC|newest]

Thread overview: 17+ 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-23  5:11       ` Christoph Hellwig
2026-04-23  9:14         ` Niklas Cassel
2026-04-23 12:17           ` Hans Holmberg
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 10:31     ` Niklas Cassel
2026-04-23  5:12       ` Christoph Hellwig [this message]
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=20260423051244.GB27929@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 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.