> * Interrupts are not under consideration right now. They land where > they land, and this may affect exclusive sets. If this is a > problem, for now, you simply lay out your hardware and exclusive > sets more intelligently.
They're easy to fix, just poke the values in /proc appropriately (same as cpus_allowed, exactly). > * Memory allocation has a tendency and preference, but no hard policy > with regards to where it comes from. A task which starts on one > part of the system but moves to another may have all its memory > allocated relatively far away. In unusual cases, it may acquire > remote memory because that's all that's left. A memory allocation > policy similar to cpus_allowed might be needed. (Martin?) The membind API already does this. M. ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
