[OMPI devel] question about Open MPI collectives on shared memory

2012-10-17 Thread Shigang Li
Dear Open MPI developers,

I'm a graduate student and recently test some minibenchmarks using Open MPI
library on Xeon X5650 cluster. From the website of Open MPI, I know that
Open MPI can use

*sm BTL* to transfer data with high bandwidth via shared memory. My
question is that what about  Open MPI collectives on shared memory? Were
they implemented and optimized on top of point-to-point communication or
utilizing shared memory separately?


Best Regards,

Shigang Li.


[OMPI devel] 1.6.3rc1 posted

2012-10-17 Thread Jeff Squyres
In the usual location:

http://www.open-mpi.org/software/ompi/v1.6/

Changes since 1.6.2:

- Add Mellanox ConnextIB IDs
- Fix rankfile when no -np is given.
- FreeBSD detection improvement.  Thanks to Brooks Davis for the
  patch.
- Removed TCP warnings on Windows.
- Improved collective algorithm selection for very large messages.
- Fix PSM MTL affinity settings.
- Fix issue with MPI_OP_COMMUTATIVE in the mpif.h bindings.  Thanks to
  Ake Sandgren for providing a patch to fix the issue.
- Fix issue with MPI_SIZEOF when using CHARACTER and LOGICAL types in
  the mpi module.  Thanks to Ake Sandgren for providing a patch to fix
  the issue.

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/




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

2012-10-17 Thread Gutierrez, Samuel K
Hi,

I'm trying to run with CMA support, but process_vm_readv is failing with EPERM 
when trying to use it as a regular user (everything seems to work fine as 
root). I've looked around for some solutions, but I can't seem to find what I'm 
looking for. The documentation states that the target and source processes need 
to have the same GID and UID to work properly. It appears that they do, so my 
feeling is that I'm missing something.

Any help is greatly appreciated.

Thanks,

Sam


[OMPI devel] [patch] SEGV on processing unexpected messages

2012-10-17 Thread Kawashima, Takahiro
Hi Open MPI developers,

I found another issue in Open MPI.

In MCA_PML_OB1_RECV_FRAG_INIT macro in ompi/mca/pml/ob1/pml_ob1_recvfrag.h
file, we copy a PML header from an arrived message to another buffer,
as follows:

frag->hdr = *(mca_pml_ob1_hdr_t*)hdr;

On this copy, we cast hdr to mca_pml_ob1_hdr_t, which is a union
of all actual header structs such as mca_pml_ob1_match_hdr_t.
This means we copy the buffer of the size of the largest header
even if the arrived message is smaller than it. This can cause
SEGV if the arrived message is small and it is laid on the bottom
of the page. Actually, my tofu BTL, the BTL component of Fujitsu
MPI for K computer, suffered from this.

The attached patch will be one of possible fixes for this issue.
This fix assume that the arrived header has at least segs[0].seg_len
bytes. This is always true for current Open MPI code because hdr
equals to segs[0].seg_addr.pval. There may exist a smarter fix.

Regards,

Takahiro Kawashima,
MPI development team,
Fujitsu
Index: ompi/mca/pml/ob1/pml_ob1_recvfrag.h
===
--- ompi/mca/pml/ob1/pml_ob1_recvfrag.h	(revision 27446)
+++ ompi/mca/pml/ob1/pml_ob1_recvfrag.h	(working copy)
@@ -69,7 +69,9 @@
 unsigned char* _ptr = (unsigned char*)frag->addr;   \
 /* init recv_frag */\
 frag->btl = btl;\
-frag->hdr = *(mca_pml_ob1_hdr_t*)hdr;   \
+_size = (segs[0].seg_len < sizeof(mca_pml_ob1_hdr_t)) ? \
+segs[0].seg_len : sizeof(mca_pml_ob1_hdr_t);\
+memcpy( &frag->hdr, hdr, _size);\
 frag->num_segments = 1; \
 _size = segs[0].seg_len;\
 for( i = 1; i < cnt; i++ ) {\
Copyright (c) 2012   FUJITSU LIMITED.  All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer listed
in this license in the documentation and/or other materials
provided with the distribution.

* Neither the name of the copyright holders nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.

The copyright holders provide no reassurances that the source code
provided does not infringe any patent, copyright, or any other
intellectual property rights of third parties.  The copyright holders
disclaim any liability to any recipient for claims brought against
recipient by any third party for infringement of that parties
intellectual property rights.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.