From: Tejun Heo <tj@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH v2 2/4] Workqueue: add system_dfl_wq
Date: Tue, 10 Jun 2025 11:44:59 -1000 [thread overview]
Message-ID: <aEinW8EpI2x6JrnO@slm.duckdns.org> (raw)
In-Reply-To: <CAAofZF7KRtTzLk7hhBSAirQ=sstmQG2gxGtbTW6LseNFzrxK1g@mail.gmail.com>
Hello,
On Tue, Jun 10, 2025 at 10:56:13AM +0200, Marco Crivellari wrote:
> >What is the reason for removing system_unbound_wq? I believe system_unbound_wq
> >is a perfectly appropriate and descriptive name for its callers. I’m not opposed
> >to system_dfl_wq as long as it will be an alias for system_unbound_wq (or even
> >system_percpu_wq, if that can be configured at boot time by sysadim).
>
> The rename to system_dfl_wq is mostly to make sure this is the default wq choice
> when per-cpu is not strictly needed.
> It has been proposed here, anyhow:
>
> https://lore.kernel.org/all/Z79E_gbWm9j9bkfR@slm.duckdns.org/
I think we ultimately want to converge on one thing and I think it does make
sense to make one behavior default over the other. ie. If we make percpu the
flavor that requires explicit designation, unbound by default becomes the
default. ie. I don't want a situation where there are system_percpu_wq and
system_unbound_wq as it's not clear which one is preferred, and if we add
system_dfl_wq to clarify the situation, at least in the long term, having
another alias for it makes things unnecessarily confusing.
So, if we're flipping the default, I'd rather remove the unbound name from
the interface. We can keep using unbound inside workqueue implementation of
course.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-06-10 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 10:35 [PATCH v2 0/4] Workqueue: rename system workqueue and add WQ_PERCPU Marco Crivellari
2025-06-09 10:35 ` [PATCH v2 1/4] Workqueue: add system_percpu_wq Marco Crivellari
2025-06-09 10:35 ` [PATCH v2 2/4] Workqueue: add system_dfl_wq Marco Crivellari
2025-06-10 3:04 ` Lai Jiangshan
2025-06-10 8:56 ` Marco Crivellari
2025-06-10 21:44 ` Tejun Heo [this message]
2025-06-09 10:35 ` [PATCH v2 3/4] Workqueue: add WQ_PERCPU Marco Crivellari
2025-06-10 2:07 ` kernel test robot
2025-06-09 10:35 ` [PATCH v2 4/4] [Doc] " Marco Crivellari
2025-06-09 18:59 ` [PATCH v2 0/4] Workqueue: rename system workqueue and " Tejun Heo
2025-06-10 8:34 ` Marco Crivellari
2025-06-10 21:38 ` Tejun Heo
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=aEinW8EpI2x6JrnO@slm.duckdns.org \
--to=tj@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=tglx@linutronix.de \
/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®