[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAAofZF7G1A2d5ShUSQbu9rn-L3XKNveULojhpyuFMnqY4=oR8w@mail.gmail.com>
Date: Thu, 20 Nov 2025 10:08:17 +0100
From: Marco Crivellari <marco.crivellari@...e.com>
To: "Martin K. Petersen" <martin.petersen@...cle.com>
Cc: linux-kernel@...r.kernel.org, MPT-FusionLinux.pdl@...adcom.com,
linux-scsi@...r.kernel.org, Tejun Heo <tj@...nel.org>,
Lai Jiangshan <jiangshanlai@...il.com>, Frederic Weisbecker <frederic@...nel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>, Michal Hocko <mhocko@...e.com>,
Sathya Prakash <sathya.prakash@...adcom.com>,
Sreekanth Reddy <sreekanth.reddy@...adcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@...adcom.com>
Subject: Re: [PATCH] scsi: message: fusion: add WQ_PERCPU to alloc_workqueue users
On Thu, Nov 20, 2025 at 5:16 AM Martin K. Petersen
<martin.petersen@...cle.com> wrote:
>
> On Fri, 07 Nov 2025 15:14:58 +0100, Marco Crivellari wrote:
>
> > Currently if a user enqueues a work item using schedule_delayed_work() the
> > used wq is "system_wq" (per-cpu wq) while queue_delayed_work() use
> > WORK_CPU_UNBOUND (used when a cpu is not specified). The same applies to
> > schedule_work() that is using system_wq and queue_work(), that makes use
> > again of WORK_CPU_UNBOUND.
> > This lack of consistency cannot be addressed without refactoring the API.
> >
> > [...]
>
> Applied to 6.19/scsi-queue, thanks!
>
> [1/1] scsi: message: fusion: add WQ_PERCPU to alloc_workqueue users
> https://git.kernel.org/mkp/scsi/c/f0dc44177ac0
>
> --
> Martin K. Petersen
Many thanks also for all the other patches / series, Martin!
--
Marco Crivellari
L3 Support Engineer, Technology & Product
Powered by blists - more mailing lists