Re: [OMPI devel] Setting AUTOMAKE_JOBS

2010-09-24 Thread George Bosilca
I would accept this behavior, at the condition that the threads are running at the lowest priority. This will give us the best of the two worlds, parallel build if the node is empty, and not a significant disturbance if I'm still busy around the computer. George. "All the books in the world

Re: [OMPI devel] Setting AUTOMAKE_JOBS

2010-09-24 Thread Paul H. Hargrove
I don't feel as strongly about this as Ralph, but do think the new behavior violates the "principle of least surprise". -Paul Ralph Castain wrote: Been thinking about this more today, and I actually find this new "feature" disturbing. It bothers me that OMPI is now dictating that it will do a

Re: [OMPI devel] Setting AUTOMAKE_JOBS

2010-09-24 Thread Ralph Castain
Been thinking about this more today, and I actually find this new "feature" disturbing. It bothers me that OMPI is now dictating that it will do a parallel build without my knowledge unless I specifically tell it not to. If it were technically possible, would we next force "make -j4"?? How would th

Re: [OMPI devel] update configury for Autoconf 2.68

2010-09-24 Thread Ralf Wildenhues
* Jeff Squyres wrote on Fri, Sep 24, 2010 at 03:26:46PM CEST: > On Sep 23, 2010, at 2:15 PM, Ralf Wildenhues wrote: > >> Is the silent-rules clause in AM_INIT_AUTOMAKE exactly equivalent to > >> calling AM_SILENT_RULES? > > > > Yes. > > Weird -- when I do this: > -AM_INIT_AUTOMAKE([foreign dist-

Re: [OMPI devel] RFC: make hwloc first-class data

2010-09-24 Thread Kenneth Lloyd
I would support making hwloc a first class element (for what it's worth, and ompi/hwloc makes sense). The INRIA paper is interesting and insightful but incomplete. It is however consistent some of our findings. The NUMA computational fabrics for various codes / data combinations may be learned by

Re: [OMPI devel] Setting AUTOMAKE_JOBS

2010-09-24 Thread Ralph Castain
I hope you'll understand if I don't run that test while on the road...one battery yank per week is my limit :-) On Fri, Sep 24, 2010 at 4:40 AM, Jeff Squyres (jsquyres) wrote: > Also to clarify: > > - did autogen set am-jobs to 2 in your case? (it should do that if lstopo > is not found - it a

Re: [OMPI devel] update configury for Autoconf 2.68

2010-09-24 Thread Jeff Squyres
On Sep 23, 2010, at 2:15 PM, Ralf Wildenhues wrote: >> Is the silent-rules clause in AM_INIT_AUTOMAKE exactly equivalent to >> calling AM_SILENT_RULES? > > Yes. Weird -- when I do this: Index: configure.ac === --- configure.ac

Re: [OMPI devel] Autogen improvements: ready for blast off

2010-09-24 Thread Jeff Squyres
Can you compare the configure stdout/stderr from an SVN checkout and a tarball -- are there differences? On Sep 23, 2010, at 4:56 PM, Ethan Mallove wrote: > We can build an SVN checkout, but with a tarball we get this: > > ... > Undefinedfirst referenced > symbol

Re: [OMPI devel] Setting AUTOMAKE_JOBS

2010-09-24 Thread Jeff Squyres (jsquyres)
Also to clarify: - did autogen set am-jobs to 2 in your case? (it should do that if lstopo is not found - it also limits itself to 4 at max) - in the same scenario, what happens if you manually set am-jobs to 1 and run autogen? Ie do you get the same heat/sluggishness? I have experienced vms

Re: [OMPI devel] Setting AUTOMAKE_JOBS

2010-09-24 Thread Ralf Wildenhues
* Ralph Castain wrote on Fri, Sep 24, 2010 at 06:41:38AM CEST: > My point is just that it is unwise to assume that the OMPI build can utilize > all available processors. I'm sure it's fine for the MTT runs, especially on > Jeff's machines as they are dedicated to that purpose - just not a good > ge

Re: [OMPI devel] Setting AUTOMAKE_JOBS

2010-09-24 Thread Ralph Castain
Sent to both for reference (see below) Just to clarify. It wasn't a deadlock situation, but rather that the machine was overloaded and running so hard that the response to keystrokes was multiple seconds. Thus, there was no way to shut it down from the keyboard or screen. Even a ctrl-c was just ge

Re: [OMPI devel] Setting AUTOMAKE_JOBS

2010-09-24 Thread Ralf Wildenhues
Hello Ralph, wow, that's not good to hear. I knew the perl ithreads implementation wasn't all that efficient, but causing a deadlock sounds like you have more trouble than just perl; at least I hope so. For reference, can you send 'perl -V' output (if you like, to the bug-automake at gnu.org lis