| 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, 02 Nov 2006 12:08:51 +0300 From: Pavel Emelianov <xemul@...nvz.org> To: Paul Menage <menage@...gle.com> CC: Matt Helsley <matthltc@...ibm.com>, vatsa@...ibm.com, Pavel Emelianov <xemul@...nvz.org>, dev@...nvz.org, sekharan@...ibm.com, ckrm-tech@...ts.sourceforge.net, balbir@...ibm.com, haveblue@...ibm.com, linux-kernel@...r.kernel.org, pj@....com, dipankar@...ibm.com, rohitseth@...gle.com Subject: Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices [snip] > I think that having a "tasks" file and a "threads" file in each > container directory would be a clean way to handle it: > > "tasks" : read/write complete process members > "threads" : read/write individual thread members I've just thought of it. Beancounter may have more than 409 tasks, while configfs doesn't allow attributes to store more than PAGE_SIZE bytes on read. So how would you fill so many tasks in one page? I like the idea of writing pids/tids to these files, but printing them back is not that easy. > > Paul > - > 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/ > - 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