linux-kernel - Re: [RFC] workqueue: avoiding unbounded wq on isolated CPUs by default

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150717152720.GD15934@mtj.duckdns.org>
Date:	Fri, 17 Jul 2015 11:27:20 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Mike Galbraith <umgwanakikbuti@...il.com>
Cc:	Daniel Bristot de Oliveira <bristot@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Lai Jiangshan <jiangshanlai@...il.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Rik van Riel <riel@...hat.com>,
	"Luis Claudio R. Goncalves" <lclaudio@...g.org>
Subject: Re: [RFC] workqueue: avoiding unbounded wq on isolated CPUs by
 default

Hello, Mike.

On Fri, Jul 17, 2015 at 06:26:30AM +0200, Mike Galbraith wrote:
> Hm, I thought the plan was that after the Lai's unbound series landed,
> his ordered wq patch would follow, but perhaps not.

Yes, that still is the plan but this is kinda unrelated to that
change.  This just initializes wq cpumask according to cpu isolation.
I'm just curious whether there was any specific reason we didn't do
this before (ISTR people discussing it back then too).

> I'm referring to the somewhat aged patch below. (freshly wedged into
> master, and maybe not properly, but it should at least look familiar).

Yeah, I think I asked Lai to try a different approach where we
regulate it from queueing path rather than playing with pwqs.  I think
that'd end up quite a bit simpler.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/