Hi Florin, > We are making some progress, but due to the learning curve required > and time constraints we focused on the performance isolation aspect > of the scheduler, so classes will get their guaranteed disk bandwidth > share,
Sounds great. Could you point me at the appropriate paper for cello. Is the algorithm it uses work preserving? I.e., if a class does not consume its guarantee, is the available bandwidth handed to other classes? How many classes can you support? We (PlanetLab) define on the order of 200 classes per system. Can you support that many? > but within the class we will use the noop scheduler. By "within a class" you simply mean the procs that are members of the class, right? How about hierarchy? Do you support that? > We will publish our patch and Good. Getting users is the first step to making it real! > hope to continue it by making it more robust and > migrating to at least the deadline scheduler. Not sure what you mean by this. Marc ------------------------------------------------------- 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
