From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.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>,
"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 0/4] replace old wq(s), added WQ_PERCPU to alloc_workqueue
Date: Wed, 12 Nov 2025 21:38:12 -0500 [thread overview]
Message-ID: <yq1wm3ud5nw.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20251031095643.74246-1-marco.crivellari@suse.com> (Marco Crivellari's message of "Fri, 31 Oct 2025 10:56:39 +0100")
Marco,
> Let's consider a nohz_full system with isolated CPUs:
> wq_unbound_cpumask is set to the housekeeping CPUs, for !WQ_UNBOUND
> the local CPU is selected.
I applied this series and your other applicable workqueue patches to
6.19/scsi-staging. But ugh, that was a lot of work.
Next time, instead of posting individual patches, please prepare one
comprehensive series for the entire subsystem and submit that as a unit
so I don't have to stitch everything together, deal with dupes, etc.
--
Martin K. Petersen
next prev parent reply other threads:[~2025-11-13 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 9:56 [PATCH 0/4] replace old wq(s), added WQ_PERCPU to alloc_workqueue Marco Crivellari
2025-10-31 9:56 ` [PATCH 1/4] scsi: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2025-10-31 9:56 ` [PATCH 2/4] scsi: qla2xxx: WQ_PERCPU added to alloc_workqueue users Marco Crivellari
2025-10-31 9:56 ` [PATCH 3/4] scsi: scsi_dh_alua: " Marco Crivellari
2025-10-31 9:56 ` [PATCH 4/4] scsi: scsi_transport_fc: " Marco Crivellari
2025-11-03 18:21 ` Justin Tee
2025-11-13 2:38 ` Martin K. Petersen [this message]
2025-11-13 8:55 ` [PATCH 0/4] replace old wq(s), added WQ_PERCPU to alloc_workqueue Marco Crivellari
2025-11-20 4:15 ` Martin K. Petersen
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=yq1wm3ud5nw.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--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