mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Junxuan Liao <ljx@cs.wisc.edu>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: btrfs thread_pool_size logic out of sync with workqueue
Date: Wed, 30 Apr 2025 08:46:04 -1000	[thread overview]
Message-ID: <aBJv7AuXubBDQNIq@slm.duckdns.org> (raw)
In-Reply-To: <53a8e583-f3bf-4efc-afa5-fe9d8af287a9@cs.wisc.edu>

On Tue, Apr 29, 2025 at 04:26:52PM -0500, Junxuan Liao wrote:
> On 4/29/25 4:15 PM, Junxuan Liao wrote:
> > So versions from 6.6 to 6.8 do have the bug, right? I guess the
> > performance regression isn't easy to trigger so no one noticed and
> > reported it.
> 
> My bad. I missed that it has already been reported in 2023.
> https://lore.kernel.org/all/dbu6wiwu3sdhmhikb2w6lns7b27gbobfavhjj57kwi2quafgwl@htjcc5oikcr3/

Yeah, the changes were too invasive to backport through -stable especially
at the time as I didn't know how well the new scheme would work. There have
been some updates afterwards but it seemed to have held up fine, so if some
distros wanna backport them, this should be pretty safe now. However, I
think the window has already passed for -stable backports.

Thanks.

-- 
tejun

      reply	other threads:[~2025-04-30 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-28 23:23 Junxuan Liao
2025-04-29 18:12 ` Tejun Heo
2025-04-29 18:28   ` Junxuan Liao
2025-04-29 18:35     ` Tejun Heo
2025-04-29 21:15       ` Junxuan Liao
2025-04-29 21:26         ` Junxuan Liao
2025-04-30 18:46           ` Tejun Heo [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=aBJv7AuXubBDQNIq@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=jiangshanlai@gmail.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljx@cs.wisc.edu \
    /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

all inboxes | Powered by JetHome®