| 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
| ||
|
Message-Id: <20060804002423.13a37eae.akpm@osdl.org> Date: Fri, 4 Aug 2006 00:24:23 -0700 From: Andrew Morton <akpm@...l.org> To: dipankar@...ibm.com Cc: vatsa@...ibm.com, mingo@...e.hu, nickpiggin@...oo.com.au, sam@...ain.net, linux-kernel@...r.kernel.org, dev@...nvz.org, efault@....de, balbir@...ibm.com, sekharan@...ibm.com, nagar@...son.ibm.com, haveblue@...ibm.com, pj@....com Subject: Re: [RFC, PATCH 0/5] Going forward with Resource Management - A cpu controller On Fri, 4 Aug 2006 12:40:09 +0530 Dipankar Sarma <dipankar@...ibm.com> wrote: > > So my take was "looks good, done deal - let's go get some sane controllers > > working". And now this! > > My recollection from the BoF is that people felt interface wasn't a major > issue and it wasn't discussed much. Most of the discussion centered > around grouping of tasks and the mem/cpu controllers and some additional > resource control requirements from openvz folks. OK. That's certainly the area to be concentrating on. > One way to go forward with the interface could be to request Chandra > to repost the ckrm infrastructure and see if the stake holders (primarily > container folks) can review and agree on it. Fine. But let's separate that activity from the primary one: worrying about the controllers. - 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