| 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: Wed, 8 Nov 2006 10:42:57 +0530 From: Srivatsa Vaddagiri <vatsa@...ibm.com> To: Paul Jackson <pj@....com> Cc: "Paul Menage" <menage@...gle.com>, dev@...nvz.org, sekharan@...ibm.com, ckrm-tech@...ts.sourceforge.net, balbir@...ibm.com, haveblue@...ibm.com, linux-kernel@...r.kernel.org, matthltc@...ibm.com, dipankar@...ibm.com, rohitseth@...gle.com Subject: Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices On Tue, Nov 07, 2006 at 07:15:18PM -0800, Paul Jackson wrote: > It goes like this ... grab a cup of coffee. Thanks for the nice and big writeup! > Each directory in a container file system has a file called 'tasks' > listing the pids of the tasks (newline separated decimal ASCII format) > in that partition element. As was discussed in a previous thread, having a 'threads' file also will be good. http://lkml.org/lkml/2006/11/1/386 > Because containers define a partition of the tasks in a system, each > task will always be in exactly one of the partition elements of a > container file system. Tasks are moved from one partition element > to another by writing their pid (decimal ASCII) into the 'tasks' > file of the receiving directory. Writing to 'tasks' file will move that single thread to the new container. Writing to 'threads' file will move all the threads of the process into the new container. -- Regards, vatsa - 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