linux-kernel - Re: [PATCH 1/2] wifi: rtlwifi: add WQ_PERCPU to alloc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAAofZF4RK7Dt=eJAXjn0Nbmw4rR_RJ4Nc4P3LkmRDCE_dvK6dQ@mail.gmail.com>
Date: Mon, 17 Nov 2025 11:02:47 +0100
From: Marco Crivellari <marco.crivellari@...e.com>
To: Ping-Ke Shih <pkshih@...ltek.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, 
	"linux-wireless@...r.kernel.org" <linux-wireless@...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>
Subject: Re: [PATCH 1/2] wifi: rtlwifi: add WQ_PERCPU to alloc_workqueue users

Hi,

On Mon, Nov 17, 2025 at 1:53 AM Ping-Ke Shih <pkshih@...ltek.com> wrote:
> [...]
>
> I think this driver should use WQ_UNBOUND as well as another patch in this
> patchset.
>
>
> I feel most user scenarios should be WQ_UNBOUND. Could you share which case
> uses WQ_PERCPU?

I think a typical scenario is when per-cpu variables are used.
But this is not the case here, for both the patches.

So yes, unless there is the need to have the item scheduled on the same CPU,
this can be converted to WQ_UNBOUND.

I did the same for other series in other subsystems. If you want, I
can send the v2
with the change.

Thanks!
--

Marco Crivellari

L3 Support Engineer, Technology & Product