linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Zorro Lang <zlang@kernel.org>,
	Hans Holmberg <hans.holmberg@wdc.com>,
	fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 01/15] common: add a _filter_rgno helper
Date: Wed, 7 May 2025 14:06:14 -0700	[thread overview]
Message-ID: <20250507210614.GH25675@frogsfrogsfrogs> (raw)
In-Reply-To: <20250507051249.3898395-2-hch@lst.de>

On Wed, May 07, 2025 at 07:12:21AM +0200, Christoph Hellwig wrote:
> Based on the existing _filter_agno helper.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  common/xfs | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/common/xfs b/common/xfs
> index 39650bac6c23..98f50e6dc04b 100644
> --- a/common/xfs
> +++ b/common/xfs
> @@ -2274,3 +2274,13 @@ _scratch_find_rt_metadir_entry() {
>  
>  	return 1
>  }
> +
> +# extract the realtime grou number from xfs_bmap output
> +_filter_rgno()
> +{
> +	# the rg number is in column 4 of xfs_bmap output
> +	perl -ne '
> +		$rg = (split /\s+/)[4] ;
> +		if ($rg =~ /\d+/) {print "$rg "} ;
> +	'
> +}

Er... maybe this should be called _filter_bmap_gno (and go in
common/filter) and then we can change the one caller of _filter_agno?

--D

> -- 
> 2.47.2
> 
> 

  reply	other threads:[~2025-05-07 21:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07  5:12 new tests for zoned xfs v2 Christoph Hellwig
2025-05-07  5:12 ` [PATCH 01/15] common: add a _filter_rgno helper Christoph Hellwig
2025-05-07 21:06   ` Darrick J. Wong [this message]
2025-05-07  5:12 ` [PATCH 02/15] add a new rw_hint helper Christoph Hellwig
2025-05-07  5:12 ` [PATCH 03/15] xfs: add a test for zoned block accounting after remount Christoph Hellwig
2025-05-07  5:12 ` [PATCH 04/15] xfs: add a zoned growfs test Christoph Hellwig
2025-05-07  5:12 ` [PATCH 05/15] xfs: add test to check for block layer reordering Christoph Hellwig
2025-05-07  5:12 ` [PATCH 06/15] xfs: add a test to check that data growfs fails with internal rt device Christoph Hellwig
2025-05-07  5:12 ` [PATCH 07/15] xfs: add a test for write lifetime hints Christoph Hellwig
2025-05-07  5:12 ` [PATCH 08/15] xfs: add a test for writeback after close Christoph Hellwig
2025-05-07  5:12 ` [PATCH 09/15] xfs: test zone stream separation for two direct writers Christoph Hellwig
2025-05-07  5:12 ` [PATCH 10/15] xfs: test zone stream separation for two buffered writers Christoph Hellwig
2025-05-07  5:12 ` [PATCH 11/15] xfs: test zoned ENOSPC behavior with multiple writers Christoph Hellwig
2025-05-07  5:12 ` [PATCH 12/15] xfs: test zoned GC file defragmentation for sequential writers Christoph Hellwig
2025-05-07  5:12 ` [PATCH 13/15] xfs: test zoned GC file defragmentation for random writers Christoph Hellwig
2025-05-07  5:12 ` [PATCH 14/15] xfs: test that xfs_repair does not mess up the zone used counter Christoph Hellwig
2025-05-07  5:12 ` [PATCH 15/15] xfs: test that truncate does not spuriously return ENOSPC Christoph Hellwig

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=20250507210614.GH25675@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hans.holmberg@wdc.com \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@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;
as well as URLs for NNTP newsgroup(s).