Messages in this thread | | | Date | Fri, 30 Apr 2004 17:41:18 +0100 | From | Christoph Hellwig <> | Subject | Re: [RFC] Revised CKRM release |
| |
> The basic concepts and motivation of CKRM remain the same as described > in the overview at http://ckrm.sf.net. Privileged users can define > classes consisting of groups of kernel objects (currently tasks and > sockets) and specify shares for these classes. Resource controllers, > which are independent of each other, can regulate and monitor the > resources consumed by classes e.g the CPU controller will control the > CPU time received by a class etc. Optional classification engines, > implemented as kernel modules, can assist in the automatic > classification of the kernel objects (tasks/sockets currently) into > classes.
I'd still love to see practical problems this thing is solving. It's a few thousand lines of code, not written to linux style guidelines, sometimes particularly obsfucated with callbacks all over the place.
I'd hate to see this in the kernel unless there's a very strong need for it and no way to solve it at a nicer layer of abstraction, e.g. userland virtual machines ala uml/umlinux.
- 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/
| |