Hi,
on Fedora 8 x86_64 openmpi-1.2.4 doesn't compile.
A quick glance at the nightly openmpi snapshot leads me to the
conclusion that
this is still the case.
In function 'open',
inlined from 'orte_abort' at runtime/orte_abort.c:91:
/usr/inc
Per my prior mail, I just filed a patch on CMR #1198 to print a big
warning on MPI_COMM_WORLD rank 0 if MPI_THREAD_MULTIPLE and/or
progress threads are used. We know that this functionality basically
doesn't work, so instead of getting lots more mail to the users list,
let's at least put a
Slight word usage and grammar error in the openib btl help test. I
believe the change below is the intended meaning.
Thanks,
Jon
Index: ompi/mca/btl/openib/help-mpi-btl-openib.txt
===
--- ompi/mca/btl/openib/help-mpi-btl-openib.txt
Cool; thanks. Go ahead and commit.
BTW, we work a bit differently here in OMPI as compared to the
OpenFabrics community -- you don't need to mail all patches to the
list before committing (especially for trivial fixes like this :-) ).
On Dec 10, 2007, at 4:05 PM, Jon Mason wrote:
Sligh
On Mon, Dec 10, 2007 at 04:14:57PM -0500, Jeff Squyres wrote:
> Cool; thanks. Go ahead and commit.
Will Do.
>
> BTW, we work a bit differently here in OMPI as compared to the
> OpenFabrics community -- you don't need to mail all patches to the
> list before committing (especially for trivia
On Dec 10, 2007, at 4:49 PM, Jon Mason wrote:
BTW, we work a bit differently here in OMPI as compared to the
OpenFabrics community -- you don't need to mail all patches to the
list before committing (especially for trivial fixes like this :-) ).
Sorry, I was just trying to err on the side of c
Yo Ralph --
I see you committed this to the ORTE-future branch. Any objections to
me committing to trunk/v1.2?
(Thanks Sebastian -- stupid Fedora! ;-) )
On Dec 10, 2007, at 11:02 AM, Sebastian Schmitzdorff wrote:
Hi,
on Fedora 8 x86_64 openmpi-1.2.4 doesn't compile.
A quick glance at th
Nah, go ahead! Just change the permission to 0660 - that's a private file
that others shouldn't really perturb.
Ralph
On 12/10/07 2:59 PM, "Jeff Squyres" wrote:
> Yo Ralph --
>
> I see you committed this to the ORTE-future branch. Any objections to
> me committing to trunk/v1.2?
>
> (Thank
Open MPI defines its own malloc (by default), so malloc of glibc
is not called.
But, without calling malloc of glibc, the allocator of libhugetlbfs
to back text and dynamic data by large pages, e.g., 16MB pages on
POWER systems, is not used.
Indeed, we can build Open MPI with --with-memory-manag
On Mon, 10 Dec 2007, Peter Wong wrote:
Open MPI defines its own malloc (by default), so malloc of glibc
is not called.
But, without calling malloc of glibc, the allocator of libhugetlbfs
to back text and dynamic data by large pages, e.g., 16MB pages on
POWER systems, is not used.
Indeed, we ca
Hi Peter,
Peter Wong wrote:
Open MPI defines its own malloc (by default), so malloc of glibc
is not called.
But, without calling malloc of glibc, the allocator of libhugetlbfs
to back text and dynamic data by large pages, e.g., 16MB pages on
POWER systems, is not used.
You could modify ptmall
11 matches
Mail list logo
