The whole point is using the CKRM framework, i.e. the RCFS interface.
Beyond that, you need to write the implementation of the controller functions that implement the rcfs get/set functions. This is pretty much the core part of kernel/ckrm/ckrm_cpu_class.c.
Beyond that you can pretty much do what you want to do with the scheduler, i.e. you go and figure out how to implement share based scheduling while observing the share values set through rcfs.
If you don't want to use RCFS + Ctrl interface then there is no real marriage ..
-- Hubertus
Marc E. Fiuczynski wrote:
Hello Hubertus, Shailabh and Chandra,
Suppose one were to develop a new CPU scheduler or port one that does not use CKRM as its management framework, what are the N different things one needs to know to integrate such a CPU scheduler with CKRM?
Thanks, Marc
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
