Re: [hwloc-devel] processor restriction + lookup of pid for 1.0

2010-01-30 Thread Ashley Pittman
On 30 Jan 2010, at 14:57, Samuel Thibault wrote: > Samuel Thibault, le Sat 30 Jan 2010 15:55:00 +0100, a écrit : >> #21 implicitly does: "what cpuset they're bound to" is just an example. >> A configuration function hwloc_topology_set_pid(topology, pid) would >> mean that the discovery has to be

Re: [hwloc-devel] processor restriction + lookup of pid for 1.0

2010-01-30 Thread Samuel Thibault
Samuel Thibault, le Sat 30 Jan 2010 15:55:00 +0100, a écrit : > > 1) hwloc_topology_from_cpu/membind(pid) (or cpuset as argument) => > > restrict topology to given cpu/membind > > 2) hwloc_topology_get_from_pid(pid) reads both cpu/membind and > > administrative restrictions from another process

Re: [hwloc-devel] processor restriction + lookup of pid for 1.0

2010-01-30 Thread Samuel Thibault
Samuel Thibault, le Sat 30 Jan 2010 15:55:00 +0100, a écrit : > #21 implicitly does: "what cpuset they're bound to" is just an example. > A configuration function hwloc_topology_set_pid(topology, pid) would > mean that the discovery has to be done from the view of the given pid, > and thus the

Re: [hwloc-devel] processor restriction + lookup of pid for 1.0

2010-01-30 Thread Samuel Thibault
Brice Goglin, le Sat 30 Jan 2010 15:47:26 +0100, a écrit : > Samuel Thibault wrote: > > Brice Goglin, le Sat 30 Jan 2010 15:32:51 +0100, a écrit : > > > >> I still don't see much difference. In #12, you get_cpubind(pid=0) and > >> use the resulting cpuset to restrict our topology. In #21, you >

Re: [hwloc-devel] processor restriction + lookup of pid for 1.0

2010-01-30 Thread Brice Goglin
Samuel Thibault wrote: > Brice Goglin, le Sat 30 Jan 2010 15:32:51 +0100, a écrit : > >> I still don't see much difference. In #12, you get_cpubind(pid=0) and >> use the resulting cpuset to restrict our topology. In #21, you >> get_cpubind(another pid) and apply the cpuset to restrict our

Re: [hwloc-devel] processor restriction + lookup of pid for 1.0

2010-01-30 Thread Samuel Thibault
Brice Goglin, le Sat 30 Jan 2010 15:32:51 +0100, a écrit : > I still don't see much difference. In #12, you get_cpubind(pid=0) and > use the resulting cpuset to restrict our topology. In #21, you > get_cpubind(another pid) and apply the cpuset to restrict our topology > as well. No: the

Re: [hwloc-devel] processor restriction + lookup of pid for 1.0

2010-01-30 Thread Samuel Thibault
Brice Goglin, le Fri 29 Jan 2010 22:48:13 +0100, a écrit : > I am looking at the remaining tickets for v1.0. Assuming there are no > "critical" warning anymore, and assuming we have done enough for people > to combine network topologies (manually for now), only 2 ticket remains: > #12 support

[hwloc-devel] processor restriction + lookup of pid for 1.0

2010-01-29 Thread Brice Goglin
I am looking at the remaining tickets for v1.0. Assuming there are no "critical" warning anymore, and assuming we have done enough for people to combine network topologies (manually for now), only 2 ticket remains: #12 support user-defined processor restriction #21 Allow lookup of specific PIDs I