Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction

2010-02-15 Thread Samuel Thibault
Ashley Pittman, le Mon 15 Feb 2010 22:16:16 +, a écrit : > I suspect the right thing to do is to from my perspective is to report the > affinity rather than the cpuset then or rather whichever of the two is most > restrictive which will be the affinity if it's set and the cpuset if it's > no

Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction

2010-02-15 Thread Ashley Pittman
On 15 Feb 2010, at 22:02, Samuel Thibault wrote: > Ashley Pittman, le Mon 15 Feb 2010 21:52:29 +, a écrit : >> On 15 Feb 2010, at 21:46, Samuel Thibault wrote: I say the commit r1726 which closed #21 and am working on testing this now, it certainly appears to be what I requested. >

Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction

2010-02-15 Thread Samuel Thibault
Ashley Pittman, le Mon 15 Feb 2010 21:52:29 +, a écrit : > On 15 Feb 2010, at 21:46, Samuel Thibault wrote: > >> 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 discov

Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction

2010-02-15 Thread Ashley Pittman
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 > t

Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction

2010-02-15 Thread Samuel Thibault
Ashley Pittman, le Mon 15 Feb 2010 21:39:29 +, a écrit : > On 15 Feb 2010, at 21:29, Samuel Thibault wrote: > > > Brice Goglin, le Mon 15 Feb 2010 22:19:33 +0100, a écrit : > >> hwloc wrote: > >>> - Add a configuration flag to limit the discovery to the current binding > >>> of the process > >

Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction

2010-02-15 Thread Ashley Pittman
On 15 Feb 2010, at 21:29, Samuel Thibault wrote: > Brice Goglin, le Mon 15 Feb 2010 22:19:33 +0100, a écrit : >> hwloc wrote: >>> - Add a configuration flag to limit the discovery to the current binding >>> of the process >>> Do we still want this for 1.0? >> >> I think Ashley wanted the first i

Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction

2010-02-15 Thread Samuel Thibault
Samuel Thibault, le Mon 15 Feb 2010 22:29:55 +0100, a écrit : > Brice Goglin, le Mon 15 Feb 2010 22:19:33 +0100, a écrit : > > hwloc wrote: > > > - Add a configuration flag to limit the discovery to the current binding > > > of the process > > > Do we still want this for 1.0? > > > > I think As

Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction

2010-02-15 Thread Samuel Thibault
Brice Goglin, le Mon 15 Feb 2010 22:19:33 +0100, a écrit : > hwloc wrote: > > - Add a configuration flag to limit the discovery to the current binding > > of the process > > Do we still want this for 1.0? > > I think Ashley wanted the first item when he requested lstopo --pid > but I may be wr

Re: [hwloc-devel] [hwloc] #12: support user-defined processor restriction

2010-02-15 Thread Brice Goglin
hwloc wrote: > The get_cpubind function is already in. > There are several ways I can see > > - Add a configuration flag to limit the discovery to the current binding > of the process > - Add a configuration function to limit the discovery to a given cpuset. > To get the current binding of th