Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Zorro Lang <zlang@kernel.org>, Lukas Herbolt <lukas@herbolt.com>,
	Eric Sandeen <sandeen@sandeen.net>,
	Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs/216: disable all concurrency scaling
Date: Thu, 25 Jun 2026 09:53:40 -0700	[thread overview]
Message-ID: <20260625165340.GA6078@frogsfrogsfrogs> (raw)
In-Reply-To: <20260625132251.GA24598@lst.de>

On Thu, Jun 25, 2026 at 03:22:51PM +0200, Christoph Hellwig wrote:
> On Wed, Jun 24, 2026 at 10:44:04AM -0700, Darrick J. Wong wrote:
> > On Fri, Jun 19, 2026 at 07:09:29AM +0200, Christoph Hellwig wrote:
> > > This test currently disables log concurrency scaling, but even the
> > > data device concurrency scaling can create mismatching output on
> > > systems with a large CPU count.
> > > 
> > > Reported-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > > Tested-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> > > ---
> > >  tests/xfs/216 | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/tests/xfs/216 b/tests/xfs/216
> > > index 1749647c11f7..ce8bb528410b 100755
> > > --- a/tests/xfs/216
> > > +++ b/tests/xfs/216
> > > @@ -23,7 +23,7 @@ _cleanup()
> > >  _require_scratch
> > >  _scratch_mkfs_xfs >/dev/null 2>&1
> > >  if _scratch_mkfs_xfs_supports_concurrency -l >> $seqres.full 2>&1; then
> > > -	loop_mkfs_opts="-l concurrency=0"
> > > +	loop_mkfs_opts="-d concurrency=0 -l concurrency=0 -r concurrency=0"
> > 
> > /me notes that -lconcurrency is not compatible with -llogdev and the
> > loopdev is not formatted with SCRATCH_MKFS_OPTIONS, so this won't work
> > to disable the concurrency= mkfs options if fstests is being run with
> > SCRATCH_LOGDEV set.
> 
> Arrg.  I hate our option parsing mess.  Any good idea how we'd get
> the desired result?  Unless there's something easy I'd be tempted to
> leave it to the first person using an external log device and large
> cpu counts..

Yeah, that's me. :)

I just sent my latest batch of random fixes:
https://lore.kernel.org/fstests/178240619625.1665857.3954516357764795627.stgit@frogsfrogsfrogs/

I don't know that it's necessary to add -dconcurrency=0 for xfs/216
after that (it seemed to work for me) but I don't have any objections to
adding more:

if _mkfs_xfs_supported $loop_mkfs_opts -l concurrency=0 $loop_dev &>> $seqres.full; then
	loop_mkfs_opts="$loop_mkfs_opts -l concurrency=0"
fi
if _mkfs_xfs_supported $loop_mkfs_opts -d concurrency=0 $loop_dev &>> $seqres.full; then
	loop_mkfs_opts="$loop_mkfs_opts -d concurrency=0"
fi

--D

  reply	other threads:[~2026-06-25 16:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-19  5:09 cpu scaling fixes v2 Christoph Hellwig
2026-06-19  5:09 ` [PATCH 1/2] xfs/078: disable all concurrency scaling Christoph Hellwig
2026-06-19 22:27   ` Eric Sandeen
2026-06-19  5:09 ` [PATCH 2/2] xfs/216: " Christoph Hellwig
2026-06-19 22:27   ` Eric Sandeen
2026-06-24 17:44   ` Darrick J. Wong
2026-06-25 13:22     ` Christoph Hellwig
2026-06-25 16:53       ` Darrick J. Wong [this message]
2026-06-26  4:53   ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2026-06-18 13:48 cpu scaling fixes Christoph Hellwig
2026-06-18 13:48 ` [PATCH 2/2] xfs/216: disable all concurrency scaling Christoph Hellwig
2026-06-19  1:57   ` Shin'ichiro Kawasaki

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=20260625165340.GA6078@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lukas@herbolt.com \
    --cc=sandeen@sandeen.net \
    --cc=shinichiro.kawasaki@wdc.com \
    --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