From: hch <hch@lst.de>
To: Hans Holmberg <Hans.Holmberg@wdc.com>
Cc: Carlos Maiolino <cem@kernel.org>,
Dave Chinner <david@fromorbit.com>,
"Darrick J . Wong" <djwong@kernel.org>, hch <hch@lst.de>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xfs: add tunable threshold parameter for triggering zone GC
Date: Fri, 28 Mar 2025 12:01:27 +0100 [thread overview]
Message-ID: <20250328110127.GA20388@lst.de> (raw)
In-Reply-To: <20250325091007.24070-1-hans.holmberg@wdc.com>
On Tue, Mar 25, 2025 at 09:10:49AM +0000, Hans Holmberg wrote:
> +Zoned Filesystems
> +=================
> +
> +For zoned file systems, the following attributes are exposed in:
> +
> + /sys/fs/xfs/<dev>/zoned/
> +
> + max_open_zones (Min: 1 Default: Varies Max: UINTMAX)
> + This read-only attribute exposes the maximum number of open zones
> + available for data placement. The value is determined at mount time and
> + is limited by the capabilities of the backing zoned device, file system
> + size and the max_open_zones mount option.
This should go into 6.15-rc as a separate patch to fix my mistake of not
adding documentation for this file. (Thanks for fixing that!)
Otherwise looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2025-03-28 11:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 9:10 [PATCH] xfs: add tunable threshold parameter for triggering zone GC Hans Holmberg
2025-03-28 11:01 ` hch [this message]
2025-03-28 12:16 ` Hans Holmberg
2025-04-16 8:45 ` Carlos Maiolino
2025-04-20 9:47 ` Guenter Roeck
2025-04-20 10:53 ` Carlos Maiolino
2025-04-20 17:42 ` Guenter Roeck
2025-04-20 18:07 ` Carlos Maiolino
2025-04-20 19:13 ` Guenter Roeck
2025-04-21 8:08 ` Carlos Maiolino
2025-04-21 8:31 ` hch
2025-04-21 13:41 ` Guenter Roeck
2025-04-22 5:48 ` hch
2025-04-22 5:57 ` Guenter Roeck
2025-04-22 6:01 ` hch
2025-04-22 6:22 ` Guenter Roeck
2025-04-22 7:56 ` Carlos Maiolino
2025-04-22 7:59 ` Carlos Maiolino
2025-04-22 8:05 ` hch
2025-04-23 6:40 ` Geert Uytterhoeven
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=20250328110127.GA20388@lst.de \
--to=hch@lst.de \
--cc=Hans.Holmberg@wdc.com \
--cc=cem@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.