From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Zorro Lang <zlang@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Lukas Herbolt <lukas@herbolt.com>,
Eric Sandeen <sandeen@sandeen.net>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs/216: disable all concurrency scaling
Date: Fri, 19 Jun 2026 10:57:28 +0900 [thread overview]
Message-ID: <ajSh4IK_C7FRW8zO@shinmob> (raw)
In-Reply-To: <20260618134834.237647-3-hch@lst.de>
On Jun 18, 2026 / 15:48, 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>
Thanks, I confirmed this patch avoid the failure that I reported.
Tested-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
next prev parent reply other threads:[~2026-06-19 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 13:48 cpu scaling fixes Christoph Hellwig
2026-06-18 13:48 ` [PATCH 1/2] xfs/078: disable all concurrency scaling Christoph Hellwig
2026-06-18 13:54 ` Eric Sandeen
2026-06-18 14:23 ` Eric Sandeen
2026-06-19 1:55 ` Shin'ichiro Kawasaki
2026-06-19 4:57 ` Christoph Hellwig
2026-06-18 13:48 ` [PATCH 2/2] xfs/216: " Christoph Hellwig
2026-06-19 1:57 ` Shin'ichiro Kawasaki [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-19 5:09 cpu scaling fixes v2 Christoph Hellwig
2026-06-19 5:09 ` [PATCH 2/2] xfs/216: disable all concurrency scaling 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=ajSh4IK_C7FRW8zO@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=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=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