| 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: Tue, 3 Aug 2010 12:58:27 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Ben Blum <bblum@...rew.cmu.edu> Cc: linux-kernel@...r.kernel.org, containers@...ts.linux-foundation.org, ebiederm@...ssion.com, lizf@...fujitsu.com, matthltc@...ibm.com, menage@...gle.com, oleg@...hat.com Subject: Re: [PATCH v4 0/2] cgroups: implement moving a threadgroup's threads atomically with cgroup.procs On Fri, 30 Jul 2010 19:56:49 -0400 Ben Blum <bblum@...rew.cmu.edu> wrote: > This patch series implements a write function for the 'cgroup.procs' > per-cgroup file, which enables atomic movement of multithreaded > applications between cgroups. Writing the thread-ID of any thread in a > threadgroup to a cgroup's procs file causes all threads in the group to > be moved to that cgroup safely with respect to threads forking/exiting. > (Possible usage scenario: If running a multithreaded build system that > sucks up system resources, this lets you restrict it all at once into a > new cgroup to keep it under control.) I can see how that would be useful. No comments from anyone else? patch 1/2 makes me cry with all those ifdefs. Maybe helper functions would help, but not a lot. patch 2/2 looks very complicated. -- 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