The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Frederic Weisbecker <frederic@kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Michal Hocko <mhocko@suse.com>, Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH RFC 0/2] workqueue: Make alloc_workqueue() unbound by default
Date: Thu, 09 Jul 2026 12:19:12 -1000	[thread overview]
Message-ID: <a58e68af922cc5fcabb795bb34c7db25@kernel.org> (raw)
In-Reply-To: <20260709102510.180513-1-marco.crivellari@suse.com>

Hello, Marco.

Can we hold off on the next tree-wide sweep until we settle the direction
on the percpu/unbound unification? The change itself is behavior-neutral
and dropping WQ_UNBOUND eventually makes sense, so no objection to the
goal, I'd just rather not do another mass conversion before that's
resolved.

As for the patch, why not start by just defaulting to WQ_UNBOUND when
neither flag is specified, instead of inverting all the internal tests
now?

Thanks.

--
tejun

  parent reply	other threads:[~2026-07-09 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 10:25 [PATCH RFC 0/2] workqueue: Make alloc_workqueue() unbound by default Marco Crivellari
2026-07-09 10:25 ` [PATCH RFC 1/2] workqueue: Make unbound the default alloc_workqueue() behavior Marco Crivellari
2026-07-09 10:25 ` [PATCH RFC 2/2] docs: workqueue: Update WQ_PERCPU documentation Marco Crivellari
2026-07-09 22:19 ` Tejun Heo [this message]
2026-07-10  7:16   ` [PATCH RFC 0/2] workqueue: Make alloc_workqueue() unbound by default Marco Crivellari

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=a58e68af922cc5fcabb795bb34c7db25@kernel.org \
    --to=tj@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.crivellari@suse.com \
    --cc=mhocko@suse.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