Messages in this thread | | | Date | Wed, 20 Sep 2006 13:11:51 -0700 | From | Paul Jackson <> | Subject | Re: [ckrm-tech] [patch00/05]: Containers(V2)- Introduction |
| |
Paul M. wrote: > Rather than adding a new process container abstraction, wouldn't it > make more sense to change cpuset to make it more extensible (more > separation between resource controllers), possibly rename it to > "containers",
Without commenting one way or the other on the overall advisability of this (for lack of sufficient clues), if we did this and renamed "cpusets" to "containers", we would still want to export the /dev/cpuset interface to just the CPU/Memory controllers. Perhaps the "container" pseudo-filesystem could optionally be mounted with a "cpuset" option, that just exposed the cpuset relevant interface, or some such thing.
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.925.600.0401 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |