Re: [OMPI devel] [PATCH] Not optimal SRQ resource allocation

2009-12-04 Thread Jeff Squyres
SRQ hardware vendors -- please review and reply... More below. On Dec 2, 2009, at 10:20 AM, Vasily Philipov wrote: > diff -r a5938d9dcada ompi/mca/btl/openib/btl_openib.c > --- a/ompi/mca/btl/openib/btl_openib.cMon Nov 23 19:00:16 2009 -0800 > +++ b/ompi/mca/btl/openib/btl_openib.c

Re: [OMPI devel] Crash when using MPI_REAL8

2009-12-04 Thread Sylvain Jeaugey
There is definetly something wrong in types. OMPI_DATATYPE_MAX_PREDEFINED is set to 45, while there are 55 predefined types. When accessing ompi_op_ddt_map[ddt->id] with MPI_REAL8 (ddt->id=54), we're reading the ompi_mpi_op_bxor struct. Depending on various things (padding, uninitialized

[OMPI devel] MPI_Request teleconf next week

2009-12-04 Thread Jeff Squyres
To discuss Brian's MPI_Request RFC and the improvements he did with ROMIO's request handling recently. Webex Meeting: Date/Time: Thursday, December 10, 2009 11:00:00 AM ET To join this meeting as an attendee, click the following url: https://cisco.webex.com/cisco/j.php?ED=130394562=484033237

Re: [OMPI devel] Crash when using MPI_REAL8

2009-12-04 Thread Sylvain Jeaugey
For the record, and to try to explain why all MTT tests may have missed this "bug", configuring without --enable-debug makes the bug disappear. Still trying to figure out why. Sylvain On Thu, 3 Dec 2009, Sylvain Jeaugey wrote: Hi list, I hope this time I won't be the only one to suffer

Re: [hwloc-devel] hwloc-bind syntax

2009-12-04 Thread Jeff Squyres
On Dec 4, 2009, at 5:36 AM, Brice Goglin wrote: > > It might be good to safely ignore 0x if it's present, but that's a small > > feature enhancement that can be done at any time (I filed a future ticket). > > It seems to work actually :) Hmm -- I don't think so...? "0x1" can't pass this test

Re: [hwloc-devel] hwloc-bind syntax

2009-12-04 Thread Jeff Squyres
On Dec 4, 2009, at 5:32 AM, Ashley Pittman wrote: > > It might be good to safely ignore 0x if it's present, but that's a small > > feature enhancement that can be done at any time (I filed a future ticket). > > Maybe not relevant but it bit me so I'll say it here, using "%x" with > sscanf on a

Re: [hwloc-devel] hwloc-bind again

2009-12-04 Thread Jeff Squyres
On Dec 4, 2009, at 1:09 AM, Brice Goglin wrote: > > shell$ hwloc-bind > > > > (i.e., invoking hwloc-bind with no arguments) > > > > returns an exit status of 0. Shouldn't it return non-zero? > > Yeah maybe I'm going to interpret that as "Hell yes! Please implement. THANKS!!!" ;-) -- Jeff

Re: [hwloc-devel] Disabling X component

2009-12-04 Thread Ashley Pittman
On Fri, 2009-12-04 at 13:04 +0100, Samuel Thibault wrote: > Ashley Pittman, le Fri 04 Dec 2009 11:06:12 +, a écrit : > > The debian version of -.txt (lstopo 0.9.3rc1) leaves my terminal with > > the colours inverted after I call it, I have to do a reset to get back > > to black on grey

Re: [hwloc-devel] Disabling X component

2009-12-04 Thread Samuel Thibault
Ashley Pittman, le Fri 04 Dec 2009 11:06:12 +, a écrit : > The debian version of -.txt (lstopo 0.9.3rc1) leaves my terminal with > the colours inverted after I call it, I have to do a reset to get back > to black on grey background. Uh, odd. Which terminal are you using? Samuel

Re: [hwloc-devel] Disabling X component

2009-12-04 Thread Brice Goglin
Ashley Pittman wrote: > I installed the debian package of hwloc yesterday and discovered that > the default action of lstopo is to display a window with a picture in. > I guess I don't have the right development packages installed for this > to be enabled in my local build. > > In my tool I want

[hwloc-devel] Disabling X component

2009-12-04 Thread Ashley Pittman
I installed the debian package of hwloc yesterday and discovered that the default action of lstopo is to display a window with a picture in. I guess I don't have the right development packages installed for this to be enabled in my local build. In my tool I want to ensure the text version is

Re: [hwloc-devel] hwloc-bind syntax

2009-12-04 Thread Brice Goglin
Jeff Squyres wrote: > It might be good to safely ignore 0x if it's present, but that's a small > feature enhancement that can be done at any time (I filed a future ticket). > It seems to work actually :) >> We might want to drop the Linux "cpuset" word and use "cgroup" instead. >> Both are

Re: [hwloc-devel] hwloc-bind syntax

2009-12-04 Thread Ashley Pittman
On Thu, 2009-12-03 at 20:32 -0500, Jeff Squyres wrote: > > > Ah, ok. To be clear, is it accurate to say that it is one of the > > > following forms: > > > > > > - a hex number (without leading "0x" -- would "0x" be ignored if it is > > > supplied?) > > > > We never used 0x there. > > Ok. > >

Re: [hwloc-devel] hwloc-bind again

2009-12-04 Thread Brice Goglin
Jeff Squyres wrote: > I notice that > > shell$ hwloc-bind > > (i.e., invoking hwloc-bind with no arguments) > > returns an exit status of 0. Shouldn't it return non-zero? I'd think it was > an error if you didn't give hwloc-bind anything to do. For example, we > wouldn't want a script with