On 9/21/06, Chandra Seetharaman <[EMAIL PROTECTED]> wrote: > Think about what will be available to customer through a distro. > > There are two (competing) memory controllers in the kernel. But, distro > can turn only one ON. Which in turn mean
Why's that? I don't see why cpuset memory nodemasks can't coexist with, say, the RG memory controller. They're attempting to solve different problems, and I can see situations where you might want to use both at once. > > So, IMHO, it is better to sort out the differences before we get things > in mainline kernel. Agreed, if we can come up with a definition of e.g. memory controller that everyone agrees is suitable for their needs. You're assuming that's so a priori, I'm not yet convinced. And I'm not trying to get another memory controller into the kernel, I'm just trying to get a standard process aggregation into the kernel (or rather, take the one that's already in the kernel and make it possible to hook other controller frameworks into it), so that the various memory controllers can become less intrusive patches in their own right. Paul ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
