[hwloc-devel] Create success (hwloc r1.7a1r5235)

Creating nightly hwloc snapshot SVN tarball was a success. Snapshot: hwloc 1.7a1r5235 Start time: Mon Jan 7 21:01:01 EST 2013 End time: Mon Jan 7 21:05:10 EST 2013 Your friendly daemon, Cyrador

Re: [hwloc-devel] v1.7

On Mon, Jan 7, 2013 at 11:00 AM, Jeff Squyres (jsquyres) wrote: > On Jan 7, 2013, at 1:42 PM, Brice Goglin > wrote: > > > My first code did that (with "all" instead of "*" because come shells > > don't like * :) > > Oh, right -- duh! :-) > > > But

Re: [hwloc-devel] v1.7

Jeff Squyres (jsquyres), le Mon 07 Jan 2013 20:01:44 +0100, a écrit : > So if you don't know the list of available components, is it not possible to > specify *only* foo and bar should be used? foo,bar,stop will do it. Samuel

Re: [hwloc-devel] v1.7

Le 07/01/2013 19:18, Jeff Squyres (jsquyres) a écrit : > On Jan 7, 2013, at 12:59 PM, Samuel Thibault > wrote: > >> Because I may not know *everything* that I want. Who knows what >> proprietary plugin I need to use to discover CPUs, while I know that for >> GPUs I can

Re: [hwloc-devel] v1.7

Brice Goglin, le Mon 07 Jan 2013 19:11:02 +0100, a écrit : > BTW, if we change the hwloc syntax, we may want to not use ^ to avoid > confusion with OMPI. ~ and ! could work but some shells may not like them? How about '-'? I doubt anybody would want a plugin name starting with it. Samuel

Re: [hwloc-devel] v1.7

Jeff Squyres (jsquyres), le Mon 07 Jan 2013 19:19:15 +0100, a écrit : > On Jan 7, 2013, at 12:59 PM, Samuel Thibault > > Because I may not know *everything* that I want. Who knows what > > proprietary plugin I need to use to discover CPUs, while I know that for > > GPUs

Re: [hwloc-devel] v1.7

On Jan 7, 2013, at 1:18 PM, "Jeff Squyres (jsquyres)" wrote: > So you're really saying "not bar and baz, but I do want everything else." With Brice's clarification (that there's an implicit "...and all the rest" at the end of the specification), I see that my

Re: [hwloc-devel] v1.7

On Jan 7, 2013, at 1:09 PM, Brice Goglin wrote: > Your argument works for selecting among I/O components like > cuda/nvml/opencl that are all independent (like several components in > the same framework in OMPI). But it doesn't work when the order matters > between

Re: [hwloc-devel] v1.7

On Jan 7, 2013, at 12:59 PM, Samuel Thibault wrote: > Because I may not know *everything* that I want. Who knows what > proprietary plugin I need to use to discover CPUs, while I know that for > GPUs I can use cuda, but I don't want to use nvml. > >> Taking your

Re: [hwloc-devel] v1.7

Le 07/01/2013 17:59, Jeff Squyres (jsquyres) a écrit : > On Jan 7, 2013, at 9:05 AM, Samuel Thibault wrote: > >> HWLOC_COMPONENTS=^cuda,opencl >> >> disables cuda *and* opencl, while intuition would have told me that it >> disables cuda but enables opencl. >> >> Also,

Re: [hwloc-devel] v1.7

On Jan 7, 2013, at 9:05 AM, Samuel Thibault wrote: > HWLOC_COMPONENTS=^cuda,opencl > > disables cuda *and* opencl, while intuition would have told me that it > disables cuda but enables opencl. > > Also, one would for instance want to be able to do this: > >

Re: [hwloc-devel] v1.7

On Jan 7, 2013, at 6:05 AM, Samuel Thibault wrote: > Hello, > > Brice Goglin, le Mon 31 Dec 2012 10:05:41 +0100, a écrit : >> + The HWLOC_COMPONENTS may now start with '^' to only define a list of >> components to exclude. > > I'm finding it not intuitive and not

Re: [hwloc-devel] v1.7

Brice Goglin, le Mon 07 Jan 2013 17:33:47 +0100, a écrit : > Ideally, we could even have a OS device for each OpenCL platform, each > containing OS devices for devices of the platform. But I'd rather keep a > single level to match other OS devices. In most cases the platform object wouldn't bring

Re: [hwloc-devel] v1.7

Le 07/01/2013 14:35, Samuel Thibault a écrit : > Brice Goglin, le Mon 31 Dec 2012 10:05:41 +0100, a écrit : >> - They add OS devices such as opencl0p0, > I see that platform 0 device 3 would be called opencl3p0. I find it > counterintuitive, and would have rather called it opencl0d3, along the

Re: [hwloc-devel] v1.7

Hello, Brice Goglin, le Mon 31 Dec 2012 10:05:41 +0100, a écrit : > + The HWLOC_COMPONENTS may now start with '^' to only define a list of > components to exclude. I'm finding it not intuitive and not generic enough, I'm wondering how that didn't affect Open-MPI, which as IUI uses this

Re: [hwloc-devel] v1.7

Brice Goglin, le Mon 31 Dec 2012 10:05:41 +0100, a écrit : > - They add OS devices such as opencl0p0, I see that platform 0 device 3 would be called opencl3p0. I find it counterintuitive, and would have rather called it opencl0d3, along the line of sda3, eth0:3, socket:2.core:0, etc. What do