Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Andrey Albershteyn <aalbersh@kernel.org>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/4] mkfs: split zone reset from discard
Date: Wed, 29 Oct 2025 08:40:50 -0700	[thread overview]
Message-ID: <20251029154050.GA3356773@frogsfrogsfrogs> (raw)
In-Reply-To: <20251029090737.1164049-5-hch@lst.de>

On Wed, Oct 29, 2025 at 10:07:32AM +0100, Christoph Hellwig wrote:
> Zone reset is a mandatory part of creating a file system on a zoned
> device, unlike discard, which can be skipped.  It also is implemented
> a bit different, so just split the handling.  This also means that we
> can now support the -K option to skip discard on the data section for
> zoned file systems.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Nice feature improvement! ;)
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

> ---
>  mkfs/xfs_mkfs.c | 112 +++++++++++++++++++++++-------------------------
>  1 file changed, 53 insertions(+), 59 deletions(-)
> 
> diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> index 09a69af31be5..cd4f3ba4a549 100644
> --- a/mkfs/xfs_mkfs.c
> +++ b/mkfs/xfs_mkfs.c
> @@ -1607,34 +1607,6 @@ discard_blocks(int fd, uint64_t nsectors, int quiet)
>  		printf("Done.\n");
>  }
>  
> -static void
> -reset_zones(
> -	struct mkfs_params	*cfg,
> -	int			fd,
> -	uint64_t		start_sector,
> -	uint64_t		nsectors,
> -	int			quiet)
> -{
> -	struct blk_zone_range range = {
> -		.sector		= start_sector,
> -		.nr_sectors	= nsectors,
> -	};
> -
> -	if (!quiet) {
> -		printf("Resetting zones...");
> -		fflush(stdout);
> -	}
> -
> -	if (ioctl(fd, BLKRESETZONE, &range) < 0) {
> -		if (!quiet)
> -			printf(" FAILED (%d)\n", -errno);
> -		exit(1);
> -	}
> -
> -	if (!quiet)
> -		printf("Done.\n");
> -}
> -
>  static __attribute__((noreturn)) void
>  illegal_option(
>  	const char		*value,
> @@ -3780,41 +3752,66 @@ discard_devices(
>  	struct zone_topology	*zt,
>  	int			quiet)
>  {
> -	/*
> -	 * This function has to be called after libxfs has been initialized.
> -	 */
> -
>  	if (!xi->data.isfile) {
>  		uint64_t	nsectors = xi->data.size;
>  
> -		if (cfg->rtstart && zt->data.nr_zones) {
> -			/*
> -			 * Note that the zone reset here includes the LBA range
> -			 * for the data device.
> -			 *
> -			 * This is because doing a single zone reset all on the
> -			 * entire device (which the kernel automatically does
> -			 * for us for a full device range) is a lot faster than
> -			 * resetting each zone individually and resetting
> -			 * the conventional zones used for the data device is a
> -			 * no-op.
> -			 */
> -			reset_zones(cfg, xi->data.fd, 0,
> -					cfg->rtstart + xi->rt.size, quiet);
> +		if (cfg->rtstart && zt->data.nr_zones)
>  			nsectors -= cfg->rtstart;
> -		}
>  		discard_blocks(xi->data.fd, nsectors, quiet);
>  	}
> -	if (xi->rt.dev && !xi->rt.isfile) {
> -		if (zt->rt.nr_zones)
> -			reset_zones(cfg, xi->rt.fd, 0, xi->rt.size, quiet);
> -		else
> -			discard_blocks(xi->rt.fd, xi->rt.size, quiet);
> -	}
> +	if (xi->rt.dev && !xi->rt.isfile && !zt->rt.nr_zones)
> +		discard_blocks(xi->rt.fd, xi->rt.size, quiet);
>  	if (xi->log.dev && xi->log.dev != xi->data.dev && !xi->log.isfile)
>  		discard_blocks(xi->log.fd, xi->log.size, quiet);
>  }
>  
> +static void
> +reset_zones(
> +	struct mkfs_params	*cfg,
> +	struct libxfs_dev	*dev,
> +	uint64_t		size,
> +	bool			quiet)
> +{
> +	struct blk_zone_range range = {
> +		.nr_sectors	= size,
> +	};
> +
> +	if (!quiet) {
> +		printf("Resetting zones...");
> +		fflush(stdout);
> +	}
> +	if (ioctl(dev->fd, BLKRESETZONE, &range) < 0) {
> +		if (!quiet)
> +			printf(" FAILED (%d)\n", -errno);
> +		exit(1);
> +	}
> +	if (!quiet)
> +		printf("Done.\n");
> +}
> +
> +static void
> +reset_devices(
> +	struct mkfs_params	*cfg,
> +	struct libxfs_init	*xi,
> +	struct zone_topology	*zt,
> +	int			quiet)
> +{
> +	/*
> +	 * Note that the zone reset here includes the conventional zones used
> +	 * for the data device.
> +	 *
> +	 * It is done that way because doing a single zone reset all on the
> +	 * entire device (which the kernel automatically does for us for a full
> +	 * device range) is a lot faster than resetting each zone individually
> +	 * and resetting the conventional zones used for the data device is a
> +	 * no-op.
> +	 */
> +	if (!xi->data.isfile && zt->data.nr_zones && cfg->rtstart)
> +		reset_zones(cfg, &xi->data, cfg->rtstart + xi->rt.size, quiet);
> +	if (xi->rt.dev && !xi->rt.isfile && zt->rt.nr_zones)
> +		reset_zones(cfg, &xi->rt, xi->rt.size, quiet);
> +}
> +
>  static void
>  validate_datadev(
>  	struct mkfs_params	*cfg,
> @@ -6196,13 +6193,10 @@ main(
>  	/*
>  	 * All values have been validated, discard the old device layout.
>  	 */
> -	if (cli.sb_feat.zoned && !discard) {
> -		fprintf(stderr,
> - _("-K not support for zoned file systems.\n"));
> -		return 1;
> -	}
>  	if (discard && !dry_run)
> -		discard_devices(&cfg, &xi, &zt, quiet);
> +		discard_devices(&cfg, cli.xi, &zt, quiet);
> +	if (cli.sb_feat.zoned && !dry_run)
> +		reset_devices(&cfg, cli.xi, &zt, quiet);
>  
>  	/*
>  	 * we need the libxfs buffer cache from here on in.
> -- 
> 2.47.3
> 
> 

      reply	other threads:[~2025-10-29 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29  9:07 improve the discard / reset zones code in mkfs Christoph Hellwig
2025-10-29  9:07 ` [PATCH 1/4] mkfs: move clearing LIBXFS_DIRECT into check_device_type Christoph Hellwig
2025-10-29 15:38   ` Darrick J. Wong
2025-10-29  9:07 ` [PATCH 2/4] libxfs: cleanup get_topology Christoph Hellwig
2025-10-29 15:39   ` Darrick J. Wong
2025-10-29  9:07 ` [PATCH 3/4] mkfs: remove duplicate struct libxfs_init arguments Christoph Hellwig
2025-10-29 15:39   ` Darrick J. Wong
2025-10-29  9:07 ` [PATCH 4/4] mkfs: split zone reset from discard Christoph Hellwig
2025-10-29 15:40   ` Darrick J. Wong [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=20251029154050.GA3356773@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=hch@lst.de \
    --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