| 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
| ||
|
Date: Thu, 28 Nov 2013 15:59:48 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Tejun Heo <htejun@...il.com> Cc: Oleg Nesterov <oleg@...hat.com>, zhang.yi20@....com.cn, lkml <linux-kernel@...r.kernel.org>, Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>, Ingo Molnar <mingo@...hat.com> Subject: Re: [PATCH]: exec: avoid propagating PF_NO_SETAFFINITY into userspace child On Thu, Nov 28, 2013 at 09:57:23AM -0500, Tejun Heo wrote: > On Thu, Nov 28, 2013 at 03:55:05PM +0100, Peter Zijlstra wrote: > > Because that is exactly what some users desire? Some RT and HPC people > > want all those crypt jobs to run on a few designated cpus and not wreck > > their compute jobs. > > And you can't do that reliably from userland. Those things are > created dynamically. workqueue provides per-workqueue attributes to > enable those use cases. It doesn't have system-wide default > attributes right now but adding that shouldn't be too difficult. Like a parent process, right? So people can use the existing task interfaces. Or are we going to tell people; here, there's cgroups for managing your tasks. Oh and here is this crippled interface X for if you want to manage these few tasks, and interface Y for managing these other few tasks. -- 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/
Powered by blists - more mailing lists