public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Hans Holmberg <Hans.Holmberg@wdc.com>
Cc: Carlos Maiolino <cem@kernel.org>,
	Dave Chinner <david@fromorbit.com>, 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: document zoned rt specifics in admin-guide
Date: Tue, 1 Apr 2025 09:15:08 -0700	[thread overview]
Message-ID: <20250401161508.GT2803749@frogsfrogsfrogs> (raw)
In-Reply-To: <20250331091333.6799-1-hans.holmberg@wdc.com>

On Mon, Mar 31, 2025 at 09:15:00AM +0000, Hans Holmberg wrote:
> Document the lifetime, nolifetime and max_open_zones mount options
> added for zoned rt file systems.
> 
> Also add documentation describing the max_open_zones sysfs attribute
> exposed in /sys/fs/xfs/<dev>/zoned/
> 
> Fixes: 4e4d52075577 ("xfs: add the zoned space allocator")
> Signed-off-by: Hans Holmberg <hans.holmberg@wdc.com>

This is consistent with what I saw when the code went by, so
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

> ---
>  Documentation/admin-guide/xfs.rst | 29 +++++++++++++++++++++++++++++
>  1 file changed, 29 insertions(+)
> 
> diff --git a/Documentation/admin-guide/xfs.rst b/Documentation/admin-guide/xfs.rst
> index b67772cf36d6..9d0344ce81f1 100644
> --- a/Documentation/admin-guide/xfs.rst
> +++ b/Documentation/admin-guide/xfs.rst
> @@ -124,6 +124,14 @@ When mounting an XFS filesystem, the following options are accepted.
>  	controls the size of each buffer and so is also relevant to
>  	this case.
>  
> +  lifetime (default) or nolifetime
> +	Enable data placement based on write life time hints provided
> +	by the user. This turns on co-allocation of data of similar
> +	life times when statistically favorable to reduce garbage
> +	collection cost.
> +
> +	These options are only available for zoned rt file systems.
> +
>    logbsize=value
>  	Set the size of each in-memory log buffer.  The size may be
>  	specified in bytes, or in kilobytes with a "k" suffix.
> @@ -143,6 +151,14 @@ When mounting an XFS filesystem, the following options are accepted.
>  	optional, and the log section can be separate from the data
>  	section or contained within it.
>  
> +  max_open_zones=value
> +	Specify the max number of zones to keep open for writing on a
> +	zoned rt device. Many open zones aids file data separation
> +	but may impact performance on HDDs.
> +
> +	If ``max_open_zones`` is not specified, the value is determined
> +	by the capabilities and the size of the zoned rt device.
> +
>    noalign
>  	Data allocations will not be aligned at stripe unit
>  	boundaries. This is only relevant to filesystems created
> @@ -542,3 +558,16 @@ The interesting knobs for XFS workqueues are as follows:
>    nice           Relative priority of scheduling the threads.  These are the
>                   same nice levels that can be applied to userspace processes.
>  ============     ===========
> +
> +Zoned Filesystems
> +=================
> +
> +For zoned file systems, the following attribute is 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.
> -- 
> 2.34.1
> 

  reply	other threads:[~2025-04-01 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31  9:15 [PATCH] xfs: document zoned rt specifics in admin-guide Hans Holmberg
2025-04-01 16:15 ` Darrick J. Wong [this message]
2025-04-03  4:25 ` hch

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=20250401161508.GT2803749@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=Hans.Holmberg@wdc.com \
    --cc=cem@kernel.org \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox