Josh and I spent some quality time on the phone today talking through
this issue. Here's some points (not in strict order):
- "--enable-static --enable-shared" (either explicit or implicit)
works fine -- it'll build both static and shared library versions of
OMPI's libraries. Unless other
Thanks for the info, Jeff.
It sounds like THREAD_SINGLE is the only known working option available
currently? Is there really a difference between that and
THREAD_FUNNELED? Like if I have 2 threads, but only the main thread is
the one making MPI calls, is that allowed? It seems to work, but I
I see this too, and had filed
http://openib.org/bugzilla/show_bug.cgi?id=188 for it. I think Jeff
opened a bug in the Open MPI bug tracker for this, he can comment on
when it is scheduled to be fixed.
Scott Weitzenkamp
SQA and Release Manager
Server Virtualization Business Unit
Cisco Systems
>
Correction. :-(
Upgrading the version of the Intel compiler worked on one platform
that I tested on, but not others. So it looks like this is still an
open issue.
On Oct 11, 2006, at 1:46 AM, Jeff Squyres wrote:
Tobias / all --
I swear there were further mails about this topic, but pe
How fast/well are MPI collectives implemented in ompi?
I'm running the Intel MPI 1.1. benchmarks and seeing the need to set
wall clock times > 12 hours for run sizes of 200 and 300 nodes for 1ppn
and 2ppn cases. The collective tests that usually pass in 2ppn cases:
Barrier, Reduce scatter, allred
On Mon, 2006-10-16 at 10:13 +0200, Åke Sandgren wrote:
> On Fri, 2006-10-06 at 00:04 -0400, Jeff Squyres wrote:
> > On 10/5/06 2:42 PM, "Michael Kluskens" wrote:
> >
> > > System: BLACS 1.1p3 on Debian Linux 3.1r3 on dual-opteron, gcc 3.3.5,
> > > Intel ifort 9.0.32 all tests with 4 processors (c
On Fri, 2006-10-06 at 00:04 -0400, Jeff Squyres wrote:
> On 10/5/06 2:42 PM, "Michael Kluskens" wrote:
>
> > System: BLACS 1.1p3 on Debian Linux 3.1r3 on dual-opteron, gcc 3.3.5,
> > Intel ifort 9.0.32 all tests with 4 processors (comments below)
> >
> > OpenMPi 1.1.1 patched and OpenMPI 1.1.2 p
On Sun, 2006-10-15 at 23:31 -0600, Josh England wrote:
> On Sat, 2006-10-14 at 09:35 -0400, Jeff Squyres wrote:
> > Given the messages from the linker and my prior mail, I'm not sure
> > that a) is possible -- it will require more poking around to know for
> > sure. b) is definitely possible s
On Sat, 2006-10-14 at 09:35 -0400, Jeff Squyres wrote:
> Given the messages from the linker and my prior mail, I'm not sure
> that a) is possible -- it will require more poking around to know for
> sure. b) is definitely possible simply by using --enable-static and
> and then using "mpicc" (
On Sat, 2006-10-14 at 09:35 -0400, Jeff Squyres wrote:
> - What exactly is your intent: a) do you want 100% static executables
> (to include the normal Linux system libraries), b) do you just want
> to avoid having to set LD_LIBRARY_PATH for some of the esoteric
> libraries such as libmpi, li
10 matches
Mail list logo
