Re: [OMPI devel] Cross Memory Attach: What am I Missing?

______ > From: devel-boun...@open-mpi.org [devel-boun...@open-mpi.org] on > behalf of Christopher Yeoh [cy...@ozlabs.org] Sent: Thursday, October > 18, 2012 5:57 PM To: de...@open-mpi.org > Subject: Re: [OMPI devel] Cross Memory Attach: What am I Missing? > > H

Re: [OMPI devel] Cross Memory Attach: What am I Missing?

Hi Sam, On Thu, 18 Oct 2012 15:08:59 + "Gutierrez, Samuel K" wrote: > > I really appreciate your pointing me in the right direction. It turns > out that on this particular system had /etc/sysctl.d/10-ptrace.conf > was set to 1. Changing this to 0 fixed the problem. I'm not

Re: [OMPI devel] MPI_THREAD_MULTIPLE testing on trunk

> On Thu, 2 Aug 2012 10:25:53 -0400 > Jeff Squyres <jsquy...@cisco.com> wrote: > > > On Aug 1, 2012, at 9:44 AM, Christopher Yeoh wrote: > > > (gdb) bt > #0 0x008039720d6c in .pthread_cond_wait () > from /lib64/power6/libpthread.so.0 #1 0x0400

[OMPI devel] MPI_THREAD_MULTIPLE testing on trunk

Hi, I was wondering if anyone else recently had tried to run trunk configured with --enable-mpi-thread-multiple and an MPI program that passed MPI_THREAD_MULTIPLE to MPI_Init_thread on a machine using the openib btl? I'm seeing even very basic programs hang. If it is working for you, what

[MTT devel] PHP5 compatibility patch applied

Hi, I have applied the PHP5 compatibility patch to trunk (from ticket #389). Note that this means the reporter code will no longer work on PHP4. Regards, Chris -- ye...@au1.ibm.com

Re: [OMPI devel] thread safety of the self btl

much need an implicit guarantee that only one thread at a time will ever call the btl self functions which manipulate those lists. Regards, Chris > george. > > On Feb 8, 2012, at 17:57 , Christopher Yeoh wrote: > > > Hi, > > > > I've noticed that the self btl d

[OMPI devel] thread safety of the self btl

Hi, I've noticed that the self btl does not do any locking. It has one lock defined but its not actually used anywhere. So I'm just wondering if that is an oversight or if there is a reason that we know for sure that there will never be concurrent access to that particular btl with threads

Re: [OMPI devel] RFC: Support Cross Memory Attach in sm btl

Hi Chris, On Fri, 13 Jan 2012 09:54:20 +1100 Christopher Samuel <sam...@unimelb.edu.au> wrote: > > On 12/01/12 20:34, Christopher Yeoh wrote: > > > Cross Memory Attach (CMA) is a pair of new syscalls > > (process_vm_readv and process_vm_writev) which allow for fast

[OMPI devel] RFC: Support Cross Memory Attach in sm btl

Hi Brad, WHAT: Adds Cross Memory Attach support to the sm btl WHY: For faster intranode communication WHERE: ompi/mca/btl/sm/ WHEN: Open MPI trunk TIMEOUT: 13/2/2012 Cross Memory Attach (CMA) is a pair of new syscalls (process_vm_readv and process_vm_writev) which allow for fast intranode

Re: [OMPI devel] Invalid free (btl_openib_endpoint.c, 448) in v1.5

On Tue, 13 Dec 2011 20:27:00 -0500 Jeff Squyres <jsquy...@cisco.com> wrote: > On Dec 13, 2011, at 7:59 PM, Christopher Yeoh wrote: > > > Sorry, late to the discussion. This is a spurious warning caused by > > passing the NULL pointer to the opal free function

Re: [OMPI devel] openib btl thread safety warning

Hi Jeff, Sorry I've been on vacation so didn't reply sooner - some comments below... On Tue, 27 Apr 2010 16:50:49 -0400 Jeff Squyres wrote: > - > #if OPAL_ENABLE_DEBUG > do { > ftr->seq = ep->eager_rdma_remote.seq; > } while

Re: [OMPI devel] mpool rdma deadlock - malloc implementation issue

y problems with this change? Regards, Chris On Mon, 2 Nov 2009 21:20:17 -0500 Jeff Squyres <jsquy...@cisco.com> wrote: > Ewww yikes. This could definitely be an issue if we weren't > (multi-thread) careful when writing these portions of the code. :-( > > > On Oct 28

Re: [OMPI devel] MPI_Grequest_start and MPI_Wait clarification

Hi Jeff, On Mon, 2 Nov 2009 21:15:15 -0500 Jeff Squyres wrote: > > I had to go re-read that whole section on generalized requests; I > agree with your analysis. Could you open a ticket and submit a > patch? You might want to look at the back ends to MPI_TEST[_ANY] >

Re: [OMPI devel] Memory corruption with mpool

Hi Mondrian, On Mon, 02 Nov 2009 13:22:11 +0100 Mondrian Nuessle wrote: > > If I turn on mpi_leave_pinned (and thus the registration cache is > actually used), I see occasional memory corruption issues for example > when I call MPI_Allreduce often. > > Debugging with

[OMPI devel] mpool rdma deadlock

Hi, I've been investigating some OpenMPI deadlocks triggered by a test suite written to test the thread safety of MPI libraries. I'm using OpenMPI 1.3.3. One of the deadlocks I'm seeing looks like this (the sleep for frame 1 is something I inserted when a deadlock is detected so I can attach a