Paul Jackson wrote: >> But "namespace" has well-established historical semantics too - a way >> of changing the mappings of local * to global objects. This >> accurately describes things liek resource controllers, cpusets, resource >> monitoring, etc. >> > > No! > > Cpusets don't rename or change the mapping of objects. > > I suspect you seriously misunderstand cpusets and are trying to cram them > into a 'namespace' remapping role into which they don't fit. >
Look, you're absolutely right, I'm stretching the terms much too far. namespaces implies some kind of domain, which is the namespace, and entities within the domain, which are the names, and there is a (task, domain) mapping. I was thinking that this implies all similar (task, domain) mappings could be treated in the same way. But when you apply this to something like cpusets, it gets a little abstract. Like the entities are (task,cpu) pairs and the domains the set of cpus that a process can run on. Sam. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
