From: Christoph Hellwig <hch@lst.de>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: Re: [PATCH v2 1/3] nvmet: replace use of system_wq with system_percpu_wq
Date: Fri, 20 Mar 2026 08:57:50 +0100 [thread overview]
Message-ID: <20260320075750.GA14771@lst.de> (raw)
In-Reply-To: <20260223102336.108512-2-marco.crivellari@suse.com>
On Mon, Feb 23, 2026 at 11:23:27AM +0100, Marco Crivellari wrote:
> system_unbound_wq -> system_dfl_wq
"dfl" is a weird acronym, that doesn't really help understanding the
code. What does it even mean?
Either way given that this has already been picked, I guess we're stuck
with it, so:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-03-20 7:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 10:23 [PATCH v2 0/3] replace old wq(s), added WQ_PERCPU to alloc_workqueue Marco Crivellari
2026-02-23 10:23 ` [PATCH v2 1/3] nvmet: replace use of system_wq with system_percpu_wq Marco Crivellari
2026-03-20 7:57 ` Christoph Hellwig [this message]
2026-03-20 8:30 ` Sebastian Andrzej Siewior
2026-02-23 10:23 ` [PATCH v2 2/3] nvme: add WQ_PERCPU to alloc_workqueue users Marco Crivellari
2026-03-20 7:58 ` Christoph Hellwig
2026-02-23 10:23 ` [PATCH v2 3/3] nvmet-fc: " Marco Crivellari
2026-03-20 7:58 ` Christoph Hellwig
2026-03-24 15:23 ` [PATCH v2 0/3] replace old wq(s), added WQ_PERCPU to alloc_workqueue Keith Busch
2026-03-24 15:30 ` 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=20260320075750.GA14771@lst.de \
--to=hch@lst.de \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=sagi@grimberg.me \
--cc=tj@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