Marc E. Fiuczynski wrote:
Vivek,
Any particular reason why you renamed ckrm_listenaq.c to ckrm_laq.c?
I'm guilty of that :-)
The reason was to achieve consistency between the name that one needs to specify for shares (res=<controller name>) and the module that one needs to load (modprobe <controller name>)
For the same reason, the erstwhile ckrm_tasks.c was renamed to ckrm_numtasks.c.
Of course, after putting out the patch yesterday, I realized I was breaking this consistency too (the I/O controller is ckrm-io but while specifying shares, one needs to use res=cki). I'll change the name needed for the latter to io (file name remains the same).
I am asking because I import the CKRM changes into our kernel tree and would like to keep track why I need to remove a particular file.
Regards, Shailabh
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
