linux-kernel - Re: [QUERY]: Is using CPU hotplug right for isolating CPUs?

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

Message-ID: <CAKohpom4vuqfVc=Bw1ak0g-7LiVT4rpLcaUTSyACEJb__1O4aQ@mail.gmail.com>
Date:	Fri, 24 Jan 2014 14:23:13 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Lei Wen <adrian.wenl@...il.com>, Kevin Hilman <khilman@...aro.org>,
	Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Linaro Networking <linaro-networking@...aro.org>,
	Tejun Heo <tj@...nel.org>
Subject: Re: [QUERY]: Is using CPU hotplug right for isolating CPUs?

On 23 January 2014 19:31, Frederic Weisbecker <fweisbec@...il.com> wrote:
> Ok, so it is fine to migrate the latter kind I guess?

Unless somebody has abused the API and used bound workqueues where he
should have used unbound ones.

> I haven't checked the details but then this quiesce option would involve
> a dependency on cpuset for any workload involving workqueues affinity. I'm
> not sure we really want this. Besides, workqueues have an existing sysfs interface
> that can be easily extended.
>
> Now indeed we may also want to enforce some policy to make sure that further
> created and queued workqueues are affine to a specific subset of CPUs. And then
> cpuset sounds like a good idea :)

Exactly. Cpuset would be more useful here. Probably we can keep both cpusets
and sysfs interface of workqueues..

I will try to add this option under cpuset which will initially move timers and
workqueues away from the cpuset in question.
--
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/