Re: [OMPI users] openmpi 1.6.3 fails to identify local host if its IP is 127.0.1.1

Hi Jeff, Ralph, first of all: thanks for your work on this! On 3 July 2013 21:09, Jeff Squyres (jsquyres) wrote: > 1. The root cause of the issue is that you are assigning a > non-existent IP address to a name. I.e., maps to 127.0.1.1, > but that IP address does not exist

Re: [OMPI users] jemalloc and crash in opal_memory_linux_ptmalloc2_open

You can build Open MPI with --without-memory-manager -- that will turn off our malloc hooks stuff. But if you're using OpenFabrics, you'll get lower bandwidth for large messages. On Jul 3, 2013, at 2:38 PM, Brian Budge wrote: > Hi all - > > I'm trying to use jemalloc

Re: [OMPI users] openmpi 1.6.3 fails to identify local host if its IP is 127.0.1.1

Ralph and I talked some more about this. Here's what we think: 1. The root cause of the issue is that you are assigning a non-existent IP address to a name. I.e., maps to 127.0.1.1, but that IP address does not exist anywhere. Hence, OMPI will never conclude that that is "local". If you

[OMPI users] jemalloc and crash in opal_memory_linux_ptmalloc2_open

Hi all - I'm trying to use jemalloc with my project, but I get a crash in opal_memory_linux_ptmalloc2_open when jemalloc is linked. If I use tcmalloc, this does not happen. Any ideas? Is there a sanctioned way to override malloc libraries in conjunction with openmpi? Thanks, Brian