On 9/20/06, Paul Jackson <[EMAIL PROTECTED]> wrote: > > The way you "associate" a file with a cpuset is to have some task in > that cpuset open that file and touch its pages -- where that task does > so before any other would be user of the file.
An alternative would be a way of binding files (or directory hierarchies) to a particular set of memory nodes. Then you wouldn't need to pre-fault the data. Extended attributes might be one way of doing it. > > Such pre-touching of files is common occurrence on the HPC (High Perf > Comp.) apps that run on the big honkin NUMA iron where cpusets were > born. I'm guessing that someone hosting 5000 web servers would rather > not deal with that particular hastle. I'm looking at it from the perspective of job control systems that need to have a good idea what big datasets the jobs running under them are touching/sharing. Paul ------------------------------------------------------------------------- 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
