On 15 Feb 2010, at 21:46, Samuel Thibault wrote: >> I'm not sure I follow ticket #12 but I suspect it's the same thing as #21. > > No, it's not, really :) > > #21 was never meant to limit the discovery to the current binding > (understand sched_setaffinity) of some process, it was just meant > to discover according to what another process would see, e.g. with > administrative constraints (understand Linux cpuset). > >> I say the commit r1726 which closed #21 and am working on testing this now, >> it certainly appears to be what I requested. > > Maybe, depending on whether you want to discover according to the other > process' binding (sched_setaffinity) or according to the other process' > restricted view of the machine (Linux cpuset).
I don't understand the difference, I thought they were two ways of achieving the same thing? -- Ashley Pittman, Bath, UK. Padb - A parallel job inspection tool for cluster computing http://padb.pittman.org.uk
