On Tue, Feb 08, 2005 at 12:42:34PM -0800, Paul Jackson wrote: > Matthew wrote: > > I found no useful and significant basis for integration of cpusets and > CKRM either involving CPU or Memory Node management. > > As best as I can figure out, CKRM is a fair share scheduler with a > gussied up more modular architecture, so that the components to track > usage, control (throttle) tasks, and classify tasks are separate > plugins. I can find no significant and useful overlap on any of these > fronts, either the existing plugins or their infrastructure, with what > cpusets has and needs. > > There are claims that CKRM has some generalized resource management > architecture that should be able to handle cpusets needs, but despite my > repeated (albeit not entirely successful) efforts to find documentation > and read source and my pleadings with Matthew and earlier on this > thread, I was never able to figure out what this meant, or find anything > that could profitably integrate with cpusets.
I thought Hubertus did talk about this when the last time the thread was active. Anyways, Here is how one could do cpuset/memset under the ckrm framework(Note that I am not pitching for a marriage :) as there are some small problems, like supporting 128 cpus, changing the parameter names that ckrm currently uses): First off cpuset and memset has to be implemented as two different controllers. cpuset controller: - 'guarantee' parameter to be used for representing cpuset(bitwise) - 'limit' parameter to be used for exclusivity and other flags. - Highest level class(/rcfs/taskclass) will have all cpus in its list - Every class will maintain two sets of cpusets, one that can be inherited, inherit_cpuset(needed when exclusive is set in a child) and the other for use by the class itself, my_cpuset. - when a new class is created (under /rcfs/taskclass), it inherits all the CPUS (from inherit_cpuset). - admin can change the cpuset of this class by echoing the new cpuset(guarantee) into the 'shares' file. - admin can set/change the exclusivity(like) flags by echoing the value(limit) to the 'shares' file. - When the exclusivity flag is set in a class, the cpuset bits in this class will be cleared in the inherit_cpuset of the parent, and all its other children. - At the time of scheduling, my_cpuset in the class of the task will be consulted. memset_controller would be similar to this, before pitching it I will talk with Matt about why he thought that there is a problem. If I missed some feature of cpuset that shows a bigger problem, please let me know. > > In sum -- I see a potential for useful integration of cpusets and > scheduler domains, I'll have to leave it up to those with expertise in > the scheduler to evaluate and perhaps accomplish this. I do not see any > useful integration of cpusets and CKRM. > > I continue to be befuddled as to why, Matthew, you confound potential > cpuset-scheddomain integration with potential cpuset-CKRM integration. > Scheduler domains and CKRM are distinct beasts, in my book, and the > contemplations of cpuset integration with these two beasts are also > distinct efforts. > > And cpusets and CKRM are distinct beasts. > > But I repeat myself ... > > -- > I won't rest till it's the best ... > Programmer, Linux Scalability > Paul Jackson <[EMAIL PROTECTED]> 1.650.933.1373, > 1.925.600.0401 > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > ckrm-tech mailing list > https://lists.sourceforge.net/lists/listinfo/ckrm-tech -- ---------------------------------------------------------------------- Chandra Seetharaman | Be careful what you choose.... - [EMAIL PROTECTED] | .......you may get it. ---------------------------------------------------------------------- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
