Quoting Paul Menage ([EMAIL PROTECTED]): > On 6/4/07, Paul Jackson <[EMAIL PROTECTED]> wrote: > > > >Yup - early in the life of cpusets, a created cpuset inherited the cpus > >and mems of its parent. But that broke the exclusive property big > >time. You will recall that a cpu_exclusive or mem_exclusive cpuset > >cannot overlap the cpus or memory, respectively, of any of its sibling > >cpusets. > > > > Maybe we could make it a per-cpuset option whether children should > inherit mems/cpus or not?
The values can be changed after the cpuset is populated, right? So really these are just defaults? Would it then make sense to just default to (parent_set - sibling_exclusive_set) for a new sibling's value? An option is fine with me, but without such an option at all, cpusets could not be applied to namespaces... thanks, -serge ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
