linux-kernel - Re: [PATCH 3/3] workqueue: Add anon workqueue sysfs hierarchy

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 22 Mar 2014 23:04:44 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Kevin Hilman <khilman@...aro.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Christoph Lameter <cl@...ux.com>,
	Mike Galbraith <bitbucket@...ine.de>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Viresh Kumar <viresh.kumar@...aro.org>
Subject: Re: [PATCH 3/3] workqueue: Add anon workqueue sysfs hierarchy

On Sat, Mar 22, 2014 at 02:55:51PM -0400, Tejun Heo wrote:
> On Sat, Mar 22, 2014 at 06:01:18PM +0100, Frederic Weisbecker wrote:
> > 1) Call a per workqueue mutex when a work execute on an ordered workqueue. Although
> >   contention should be very rare (only while we replace the workqueue attrs and
> >   switch to a new worker), frequent locking may have a visible impact.
> > 
> > 2) Have a seperate worker for all ordered workqueues. But we may lose a bit of
> >   serialization with other workqueues along the way.
> 
> Ordered workqueues are always bound to the fallback default worker
> pool.  Why not just adjust cpus_allowed of the worker pool?

Now that you tell me, that sounds obvious enough. I'll try something.

Thanks.

> 
> 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/