From: Zorro Lang <zlang@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: "Darrick J. Wong" <djwong@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: Tue, 30 Jun 2026 02:00:10 +0800 [thread overview]
Message-ID: <akKye7hMwSw3Vc8L@zlang-mailbox> (raw)
In-Reply-To: <20260626045353.GA8735@lst.de>
On Fri, Jun 26, 2026 at 06:53:53AM +0200, Christoph Hellwig wrote:
> I'll retract this patch in favour of the btrfs fix from Darrick.
> We'll still need patch 1, though.
Let me make sure I have the current status mapped out correctly. So we
should apply/merge the following patches:
[PATCH 1/2] common/xfs: fix _scratch_mkfs_xfs_supports_concurrency
[PATCH 2/2] xfs/21[67]: fix mkfs log concurrency detection
[PATCH 1/2] xfs/078: disable all concurrency scaling
And revert:
[PATCH 2/2] xfs/216: disable all concurrency scaling
Is that correct?
>
next prev parent reply other threads:[~2026-06-29 18:00 UTC|newest]
Thread overview: 14+ 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
2026-06-26 4:53 ` Christoph Hellwig
2026-06-29 18:00 ` Zorro Lang [this message]
2026-06-29 22:58 ` Darrick J. Wong
2026-06-30 5:13 ` 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=akKye7hMwSw3Vc8L@zlang-mailbox \
--to=zlang@kernel.org \
--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=shinichiro.kawasaki@wdc.com \
/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