Messages in this thread | | | Subject | Re: [ckrm-tech] [RFC] [PATCH 00/12] CKRM after a major overhaul | From | Chandra Seetharaman <> | Date | Fri, 21 Apr 2006 22:46:40 -0700 |
| |
On Sat, 2006-04-22 at 07:08 +0300, Al Boldi wrote:
> i.e: it should be possible to run the RCs w/o CKRM. > > The current design pins the RCs on CKRM, when in fact this is not necessary. > One way to decouple them, could be to pin them against pid, thus allowing an > RC to leverage the pid hierarchy w/o the need for CKRM. And only when finer > RM control is necessary, should CKRM come into play, by dynamically > adjusting the RC to achieve the desired effect.
This model works well in universities, where you associate some resource when a student logs in, or a virtualised environment (like a UML or vserver), where you attach resource to the root process.
It doesn't work with web servers, database servers etc.,, where the main application will be forking tasks for different set of end users. In that case you have to group tasks that are not related to one another and attach resources to them.
Having a unified interface gives the system administrator ability to group the tasks as they see them in real life (a department or important transactions or just critical apps in a desktop).
It also has the added advantage that the resource controller writer do not have to spend their time in coming up with an interface for their controller. On the other hand if they do, the user finally ends up with multiple interface (/proc, sysfs, configfs, /dev etc.,) to do their resource management.
> > Thanks! > > -- > Al > --
---------------------------------------------------------------------- Chandra Seetharaman | Be careful what you choose.... - sekharan@us.ibm.com | .......you may get it. ----------------------------------------------------------------------
- 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/
| |