Re: [OMPI devel] Possible bug with derived datatypes and openib BTL in trunk

[George Bosilca]

Rolf,

I didn’t see these on my check run. Can you run the MPI_Isend_ator test with 
mpi_ddt_pack_debug and mpi_ddt_unpack_debug set to 1. I would be interested in 
the output you get on your machine.

George.


On Apr 16, 2014, at 14:34 , Rolf vandeVaart  wrote:

> I have seen errors when running the intel test suite using the openib BTL 
> when transferring derived datatypes.  I do not see the error with sm or tcp 
> BTLs.  The errors begin after this checkin.
> 
> https://svn.open-mpi.org/trac/ompi/changeset/31370
> Timestamp: 04/11/14 16:06:56 (5 days ago)
> Author: bosilca
> Message: Reshape all the packing/unpacking functions to use the same 
> skeleton. Rewrite the
> generic_unpacking to take advantage of the same capabilitites.
> 
> Does anyone else see errors?  Here is an example running with r31370:
> 
> [rvandevaart@drossetti-ivy1 src]$ mpirun --mca btl self,openib -np 2 -host 
> drossetti-ivy0,drossetti-ivy1 --mca btl_openib_warn_default_gid_prefix 0 
> MPI_Isend_ator_c
> MPITEST error (1): libmpitest.c:1608 i=117, int32_t value=-1, expected 117
> MPITEST error (1): libmpitest.c:1578 i=195, char value=-1, expected -61
> MPITEST error (1): 2 errors in buffer (17,0,12) len 273 commsize 2 commtype 
> -10 data_type 13 root 1
> MPITEST error (1): libmpitest.c:1608 i=117, int32_t value=-1, expected 117
> MPITEST error (1): libmpitest.c:1578 i=195, char value=-1, expected -61
> MPITEST error (1): 2 errors in buffer (17,2,12) len 273 commsize 2 commtype 
> -16 data_type 13 root 1
> MPITEST info  (0): Starting MPI_Isend_ator: All Isend TO Root test
> MPITEST info  (0): Node spec MPITEST_comm_sizes[6]=2 too large, using 1
> MPITEST info  (0): Node spec MPITEST_comm_sizes[22]=2 too large, using 1
> MPITEST info  (0): Node spec MPITEST_comm_sizes[32]=2 too large, using 1
> MPITEST error (0): libmpitest.c:1608 i=117, int32_t value=-1, expected 118
> MPITEST error (0): libmpitest.c:1578 i=195, char value=-1, expected -60
> MPITEST error (0): 2 errors in buffer (17,0,12) len 273 commsize 2 commtype 
> -10 data_type 13 root 0
> MPITEST error (0): libmpitest.c:1608 i=117, int32_t value=-1, expected 118
> MPITEST error (0): libmpitest.c:1578 i=195, char value=-1, expected -60
> MPITEST error (0): 2 errors in buffer (17,2,12) len 273 commsize 2 commtype 
> -16 data_type 13 root 0
> MPITEST error (1): libmpitest.c:1608 i=117, int32_t value=-1, expected 117
> MPITEST error (1): libmpitest.c:1578 i=195, char value=-1, expected -61
> MPITEST error (1): 2 errors in buffer (17,4,12) len 273 commsize 2 commtype 
> -13 data_type 13 root 1
> MPITEST error (0): libmpitest.c:1608 i=117, int32_t value=-1, expected 118
> MPITEST error (0): libmpitest.c:1578 i=195, char value=-1, expected -60
> MPITEST error (0): 2 errors in buffer (17,4,12) len 273 commsize 2 commtype 
> -13 data_type 13 root 0
> MPITEST error (1): libmpitest.c:1608 i=117, int32_t value=-1, expected 117
> MPITEST error (1): libmpitest.c:1578 i=195, char value=-1, expected -61
> MPITEST error (1): 2 errors in buffer (17,6,12) len 273 commsize 2 commtype 
> -15 data_type 13 root 0
> MPITEST error (0): libmpitest.c:1608 i=117, int32_t value=-1, expected 117
> MPITEST error (0): libmpitest.c:1578 i=195, char value=-1, expected -61
> MPITEST error (0): 2 errors in buffer (17,6,12) len 273 commsize 2 commtype 
> -15 data_type 13 root 0
> MPITEST_results: MPI_Isend_ator: All Isend TO Root 8 tests FAILED (of 3744)
> ---
> Primary job  terminated normally, but 1 process returned
> a non-zero exit code.. Per user-direction, the job has been aborted.
> ---
> --
> mpirun detected that one or more processes exited with non-zero status, thus 
> causing
> the job to be terminated. The first process to do so was:
> 
>  Process name: [[12363,1],0]
>  Exit code:4
> --
> [rvandevaart@drossetti-ivy1 src]$ 
> 
> 
> Here is an error with the trunk which is slightly different.
> [rvandevaart@drossetti-ivy1 src]$ mpirun --mca btl self,openib -np 2 -host 
> drossetti-ivy0,drossetti-ivy1 --mca btl_openib_warn_default_gid_prefix 0 
> MPI_Isend_ator_c
> [drossetti-ivy1.nvidia.com:22875] 
> ../../../opal/datatype/opal_datatype_position.c:72
>   Pointer 0x1ad414c size 4 is outside [0x1ac1d20,0x1ad1d08] for
>   base ptr 0x1ac1d20 count 273 and data 
> [drossetti-ivy1.nvidia.com:22875] Datatype 0x1ac0220[] size 104 align 16 id 0 
> length 22 used 21
> true_lb 0 true_ub 232 (true_extent 232) lb 0 ub 240 (extent 240)
> nbElems 21 loops 0 flags 1C4 (commited )-c--lu-GD--[---][---]
>   contain lb ub OPAL_LB OPAL_UB OPAL_INT1 OPAL_INT2 OPAL_INT4 OPAL_INT8 
> OPAL_UINT1 OPAL_UINT2 OPAL_UINT4 OPAL_UINT8 OPAL_FLOAT4 OPAL_FLOAT8 
> OPAL_FLOAT16 
> --C---P-D--[---][---]  OPAL_INT4 count 1 disp 0x0 (0) extent 4 (size 4)
> --C---P-D--[---][---

[OMPI devel] Possible bug with derived datatypes and openib BTL in trunk

[Rolf vandeVaart]

I have seen errors when running the intel test suite using the openib BTL when 
transferring derived datatypes.  I do not see the error with sm or tcp BTLs.  
The errors begin after this checkin.

https://svn.open-mpi.org/trac/ompi/changeset/31370
Timestamp: 04/11/14 16:06:56 (5 days ago)
Author: bosilca
Message: Reshape all the packing/unpacking functions to use the same skeleton. 
Rewrite the
generic_unpacking to take advantage of the same capabilitites.

Does anyone else see errors?  Here is an example running with r31370:

[rvandevaart@drossetti-ivy1 src]$ mpirun --mca btl self,openib -np 2 -host 
drossetti-ivy0,drossetti-ivy1 --mca btl_openib_warn_default_gid_prefix 0 
MPI_Isend_ator_c
MPITEST error (1): libmpitest.c:1608 i=117, int32_t value=-1, expected 117
MPITEST error (1): libmpitest.c:1578 i=195, char value=-1, expected -61
MPITEST error (1): 2 errors in buffer (17,0,12) len 273 commsize 2 commtype -10 
data_type 13 root 1
MPITEST error (1): libmpitest.c:1608 i=117, int32_t value=-1, expected 117
MPITEST error (1): libmpitest.c:1578 i=195, char value=-1, expected -61
MPITEST error (1): 2 errors in buffer (17,2,12) len 273 commsize 2 commtype -16 
data_type 13 root 1
MPITEST info  (0): Starting MPI_Isend_ator: All Isend TO Root test
MPITEST info  (0): Node spec MPITEST_comm_sizes[6]=2 too large, using 1
MPITEST info  (0): Node spec MPITEST_comm_sizes[22]=2 too large, using 1
MPITEST info  (0): Node spec MPITEST_comm_sizes[32]=2 too large, using 1
MPITEST error (0): libmpitest.c:1608 i=117, int32_t value=-1, expected 118
MPITEST error (0): libmpitest.c:1578 i=195, char value=-1, expected -60
MPITEST error (0): 2 errors in buffer (17,0,12) len 273 commsize 2 commtype -10 
data_type 13 root 0
MPITEST error (0): libmpitest.c:1608 i=117, int32_t value=-1, expected 118
MPITEST error (0): libmpitest.c:1578 i=195, char value=-1, expected -60
MPITEST error (0): 2 errors in buffer (17,2,12) len 273 commsize 2 commtype -16 
data_type 13 root 0
MPITEST error (1): libmpitest.c:1608 i=117, int32_t value=-1, expected 117
MPITEST error (1): libmpitest.c:1578 i=195, char value=-1, expected -61
MPITEST error (1): 2 errors in buffer (17,4,12) len 273 commsize 2 commtype -13 
data_type 13 root 1
MPITEST error (0): libmpitest.c:1608 i=117, int32_t value=-1, expected 118
MPITEST error (0): libmpitest.c:1578 i=195, char value=-1, expected -60
MPITEST error (0): 2 errors in buffer (17,4,12) len 273 commsize 2 commtype -13 
data_type 13 root 0
MPITEST error (1): libmpitest.c:1608 i=117, int32_t value=-1, expected 117
MPITEST error (1): libmpitest.c:1578 i=195, char value=-1, expected -61
MPITEST error (1): 2 errors in buffer (17,6,12) len 273 commsize 2 commtype -15 
data_type 13 root 0
MPITEST error (0): libmpitest.c:1608 i=117, int32_t value=-1, expected 117
MPITEST error (0): libmpitest.c:1578 i=195, char value=-1, expected -61
MPITEST error (0): 2 errors in buffer (17,6,12) len 273 commsize 2 commtype -15 
data_type 13 root 0
MPITEST_results: MPI_Isend_ator: All Isend TO Root 8 tests FAILED (of 3744)
---
Primary job  terminated normally, but 1 process returned
a non-zero exit code.. Per user-direction, the job has been aborted.
---
--
mpirun detected that one or more processes exited with non-zero status, thus 
causing
the job to be terminated. The first process to do so was:

  Process name: [[12363,1],0]
  Exit code:4
--
[rvandevaart@drossetti-ivy1 src]$ 


Here is an error with the trunk which is slightly different.
[rvandevaart@drossetti-ivy1 src]$ mpirun --mca btl self,openib -np 2 -host 
drossetti-ivy0,drossetti-ivy1 --mca btl_openib_warn_default_gid_prefix 0 
MPI_Isend_ator_c
[drossetti-ivy1.nvidia.com:22875] 
../../../opal/datatype/opal_datatype_position.c:72
Pointer 0x1ad414c size 4 is outside [0x1ac1d20,0x1ad1d08] for
base ptr 0x1ac1d20 count 273 and data 
[drossetti-ivy1.nvidia.com:22875] Datatype 0x1ac0220[] size 104 align 16 id 0 
length 22 used 21
true_lb 0 true_ub 232 (true_extent 232) lb 0 ub 240 (extent 240)
nbElems 21 loops 0 flags 1C4 (commited )-c--lu-GD--[---][---]
   contain lb ub OPAL_LB OPAL_UB OPAL_INT1 OPAL_INT2 OPAL_INT4 OPAL_INT8 
OPAL_UINT1 OPAL_UINT2 OPAL_UINT4 OPAL_UINT8 OPAL_FLOAT4 OPAL_FLOAT8 
OPAL_FLOAT16 
--C---P-D--[---][---]  OPAL_INT4 count 1 disp 0x0 (0) extent 4 (size 4)
--C---P-D--[---][---]  OPAL_INT2 count 1 disp 0x8 (8) extent 2 (size 2)
--C---P-D--[---][---]  OPAL_INT8 count 1 disp 0x10 (16) extent 8 (size 8)
--C---P-D--[---][---] OPAL_UINT2 count 1 disp 0x20 (32) extent 2 (size 2)
--C---P-D--[---][---] OPAL_UINT4 count 1 disp 0x24 (36) extent 4 (size 4)
--C---P-D--[---][---] OPAL_UINT8 count 1 disp 0x30 (48) extent 8 (size 8)
--C---P-D--[---][---]OPAL_FLOAT4 count 1 disp 0x40 (64) 

Re: [OMPI devel] Bug in man page of MPI_Type_create_hindexed

[Jeff Squyres (jsquyres)]

Excellent catch -- thanks for letting us know.  I've committed the fix and 
slated it over to the v1.8 branch for inclusion in 1.8.1.


On Apr 16, 2014, at 7:55 AM, Bastian Beischer  
wrote:

> Dear all,
> 
> In open-mpi version 1.8 the man page of MPI_Type_create_hindexed gives this 
> declaration of the function:
> 
> int MPI_Type_create_hindexed(int count, const int array_of_blocklengths[],
> const int array_of_displacements[], MPI_Datatype oldtype,
> MPI_Datatype *newtype)
> 
> However I think the array_of_displacements should be of type MPI_Aint?
> 
> This was relevant to me because I wanted to create a datatype with large 
> offsets > INT_MAX and I didn't know I could use MPI_Type_create_hindexed 
> until a colleague pointed me to the MPI standard which says that the 
> displacements are of type MPI_Aint.
> 
> Cheers
> Bastian
> 
> -- 
> Bastian Beischer
> RWTH Aachen University of Technology
> 
> @RWTH Aachen
> Office: 28 C 203
> Phone: +49-241-80-27205
> E-mail: beisc...@physik.rwth-aachen.de
> Address: I. Physikalisches Institut B, Sommerfeldstr. 14, D-52074 Aachen
> 
> @CERN
> Office: Bdg 32-4-B12
> Phone: +41-22-76-75750
> E-mail: bastian.beisc...@cern.ch
> Address: CERN, CH-1211 Geneve 23
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/04/14540.php


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

Re: [OMPI devel] 1-question developer poll

[Adrian Reber]

On Wed, Apr 16, 2014 at 10:32:10AM +, Jeff Squyres (jsquyres) wrote:
> What source code repository technology(ies) do you use for Open MPI 
> development? (indicate all that apply)
> 
> - SVN
> - Mercurial
> - Git

git

Adrian


pgp0Qj8qxYTHc.pgp
Description: PGP signature

Re: [OMPI devel] 1-question developer poll

[Edgar Gabriel]

mostly svn, sometimes mercurial, no git.

Edgar

On 4/16/2014 5:32 AM, Jeff Squyres (jsquyres) wrote:
> What source code repository technology(ies) do you use for Open MPI 
> development? (indicate all that apply)
> 
> - SVN
> - Mercurial
> - Git
> 
> I ask this question because there's serious discussions afoot to switch 
> OMPI's main SVN repo to Git, and I want to get a feel for the current 
> landscape out there.
> 

-- 
Edgar Gabriel
Associate Professor
Parallel Software Technologies Lab  http://pstl.cs.uh.edu
Department of Computer Science  University of Houston
Philip G. Hoffman Hall, Room 524Houston, TX-77204, USA
Tel: +1 (713) 743-3857  Fax: +1 (713) 743-3335



signature.asc
Description: OpenPGP digital signature

Re: [OMPI devel] [EXTERNAL] Re: 1-question developer poll

[Saliya Ekanayake]

We went through the same situation in our lab (SVN to Git) and here are few
thoughts,

1. We wanted Git primarily to get the benefits of Github
2. Also, as it gives the option to locally version code (plus local
branches).

The downside of Git as I felt is its initial learning curve. Another is
that in SVN you could work (checkout) on subfolders, but with Git model
this is not encouraged although something similar could be done with
http://git-scm.com/docs/git-submodule

Thanks,
Saliya


On Wed, Apr 16, 2014 at 11:10 AM, Grant, Ryan Eric (-EXP) <
regr...@sandia.gov> wrote:

>  Sandia uses a mix of Git and SVN.
>
>  --Ryan
>
>   On 4/16/14 9:01 AM, "George Bosilca"  wrote:
>
>   We ate using:
>
> Mainly mercurial.
> Svn only for ompi.
> Rarely git.
>
> George.
>  On Apr 16, 2014 10:36 AM, "Rolf vandeVaart" 
> wrote:
>
>> SVN
>>
>> >-Original Message-
>> >From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Nathan
>> >Hjelm
>> >Sent: Wednesday, April 16, 2014 10:35 AM
>> >To: Open MPI Developers
>> >Subject: Re: [OMPI devel] 1-question developer poll
>> >
>> >* PGP Signed by an unknown key
>> >
>> >Git
>> >
>> >On Wed, Apr 16, 2014 at 10:32:10AM +, Jeff Squyres (jsquyres) wrote:
>> >> What source code repository technology(ies) do you use for Open MPI
>> >development? (indicate all that apply)
>> >>
>> >> - SVN
>> >> - Mercurial
>> >> - Git
>> >>
>> >> I ask this question because there's serious discussions afoot to switch
>> >OMPI's main SVN repo to Git, and I want to get a feel for the current
>> >landscape out there.
>> >>
>> >> --
>> >> Jeff Squyres
>> >> jsquy...@cisco.com
>> >> For corporate legal information go to:
>> >http://www.cisco.com/web/about/doing_business/legal/cri/
>> >>
>> >> ___
>> >> devel mailing list
>> >> de...@open-mpi.org
>> >> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> >> Link to this post: http://www.open-
>> >mpi.org/community/lists/devel/2014/04/14537.php
>> >
>> >* Unknown Key
>> >* 0x9AC22B15
>>
>> ---
>> This email message is for the sole use of the intended recipient(s) and
>> may contain
>> confidential information.  Any unauthorized review, use, disclosure or
>> distribution
>> is prohibited.  If you are not the intended recipient, please contact the
>> sender by
>> reply email and destroy all copies of the original message.
>>
>> ---
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2014/04/14546.php
>>
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/04/14548.php
>



-- 
Saliya Ekanayake esal...@gmail.com
Cell 812-391-4914 Home 812-961-6383
http://saliya.org

Re: [OMPI devel] [EXTERNAL] Re: 1-question developer poll

[Grant, Ryan Eric (-EXP)]

Sandia uses a mix of Git and SVN.

--Ryan

On 4/16/14 9:01 AM, "George Bosilca" 
mailto:bosi...@icl.utk.edu>> wrote:


We ate using:

Mainly mercurial.
Svn only for ompi.
Rarely git.

George.

On Apr 16, 2014 10:36 AM, "Rolf vandeVaart" 
mailto:rvandeva...@nvidia.com>> wrote:
SVN

>-Original Message-
>From: devel 
>[mailto:devel-boun...@open-mpi.org] On 
>Behalf Of Nathan
>Hjelm
>Sent: Wednesday, April 16, 2014 10:35 AM
>To: Open MPI Developers
>Subject: Re: [OMPI devel] 1-question developer poll
>
>* PGP Signed by an unknown key
>
>Git
>
>On Wed, Apr 16, 2014 at 10:32:10AM +, Jeff Squyres (jsquyres) wrote:
>> What source code repository technology(ies) do you use for Open MPI
>development? (indicate all that apply)
>>
>> - SVN
>> - Mercurial
>> - Git
>>
>> I ask this question because there's serious discussions afoot to switch
>OMPI's main SVN repo to Git, and I want to get a feel for the current
>landscape out there.
>>
>> --
>> Jeff Squyres
>> jsquy...@cisco.com
>> For corporate legal information go to:
>http://www.cisco.com/web/about/doing_business/legal/cri/
>>
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post: http://www.open-
>mpi.org/community/lists/devel/2014/04/14537.php
>
>* Unknown Key
>* 0x9AC22B15
---
This email message is for the sole use of the intended recipient(s) and may 
contain
confidential information.  Any unauthorized review, use, disclosure or 
distribution
is prohibited.  If you are not the intended recipient, please contact the 
sender by
reply email and destroy all copies of the original message.
---
___
devel mailing list
de...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
Link to this post: 
http://www.open-mpi.org/community/lists/devel/2014/04/14546.php

Re: [OMPI devel] 1-question developer poll

[George Bosilca]

We ate using:

Mainly mercurial.
Svn only for ompi.
Rarely git.

George.
 On Apr 16, 2014 10:36 AM, "Rolf vandeVaart"  wrote:

> SVN
>
> >-Original Message-
> >From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Nathan
> >Hjelm
> >Sent: Wednesday, April 16, 2014 10:35 AM
> >To: Open MPI Developers
> >Subject: Re: [OMPI devel] 1-question developer poll
> >
> >* PGP Signed by an unknown key
> >
> >Git
> >
> >On Wed, Apr 16, 2014 at 10:32:10AM +, Jeff Squyres (jsquyres) wrote:
> >> What source code repository technology(ies) do you use for Open MPI
> >development? (indicate all that apply)
> >>
> >> - SVN
> >> - Mercurial
> >> - Git
> >>
> >> I ask this question because there's serious discussions afoot to switch
> >OMPI's main SVN repo to Git, and I want to get a feel for the current
> >landscape out there.
> >>
> >> --
> >> Jeff Squyres
> >> jsquy...@cisco.com
> >> For corporate legal information go to:
> >http://www.cisco.com/web/about/doing_business/legal/cri/
> >>
> >> ___
> >> devel mailing list
> >> de...@open-mpi.org
> >> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> >> Link to this post: http://www.open-
> >mpi.org/community/lists/devel/2014/04/14537.php
> >
> >* Unknown Key
> >* 0x9AC22B15
>
> ---
> This email message is for the sole use of the intended recipient(s) and
> may contain
> confidential information.  Any unauthorized review, use, disclosure or
> distribution
> is prohibited.  If you are not the intended recipient, please contact the
> sender by
> reply email and destroy all copies of the original message.
>
> ---
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/04/14546.php
>

Re: [OMPI devel] 1-question developer poll

[Rolf vandeVaart]

SVN

>-Original Message-
>From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Nathan
>Hjelm
>Sent: Wednesday, April 16, 2014 10:35 AM
>To: Open MPI Developers
>Subject: Re: [OMPI devel] 1-question developer poll
>
>* PGP Signed by an unknown key
>
>Git
>
>On Wed, Apr 16, 2014 at 10:32:10AM +, Jeff Squyres (jsquyres) wrote:
>> What source code repository technology(ies) do you use for Open MPI
>development? (indicate all that apply)
>>
>> - SVN
>> - Mercurial
>> - Git
>>
>> I ask this question because there's serious discussions afoot to switch
>OMPI's main SVN repo to Git, and I want to get a feel for the current
>landscape out there.
>>
>> --
>> Jeff Squyres
>> jsquy...@cisco.com
>> For corporate legal information go to:
>http://www.cisco.com/web/about/doing_business/legal/cri/
>>
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post: http://www.open-
>mpi.org/community/lists/devel/2014/04/14537.php
>
>* Unknown Key
>* 0x9AC22B15
---
This email message is for the sole use of the intended recipient(s) and may 
contain
confidential information.  Any unauthorized review, use, disclosure or 
distribution
is prohibited.  If you are not the intended recipient, please contact the 
sender by
reply email and destroy all copies of the original message.
---

Re: [OMPI devel] Update SLURM FAQ entry?

[Jeff Squyres (jsquyres)]

Web site updated -- thanks!

On Apr 15, 2014, at 9:52 PM, Anthony Alba  wrote:

> Sure - how about this:
> 
> 
> 2. Yes, if you have configured OMPI --with-pmi=foo, where foo is the path to 
> the directory where pmi.h/pmi2.h is located. Slurm (> 2.6, > 14.03) installs 
> PMI-2 support by default. 
> 
> Older versions of Slurm install PMI-1 by default. If you desire PMI-2, Slurm 
> requires that you manually install that support. When the --with-pmi option 
> is given, OMPI will automatically determine if PMI-2 support was built and 
> use it in place of PMI-1.
> 
> 4. Any issues with Slurm 2.6.3, 14.03?
> 
> Yes. The Slurm 2.6.3, 14.03 releases have a bug in their PMI-2 support. 
> 
> For the slurm-2.6 branch,  it is recommended to use the latest version (2.6.9 
> as of 2014/4) which works with pmi2.
> 
> For the slurm-14.03 branch, the fix will be in  14.03.1. 
> 
> 
> 
> 
> 
> 
> 
> On Tue, Apr 15, 2014 at 9:46 PM, Jeff Squyres (jsquyres)  
> wrote:
> Would you mind sending us updated text?  I don't know if any of us follows 
> the SLURM releases closely...
> 
> (I assume you're referring specifically to question 4, right?)
> 
> 
> 
> On Apr 11, 2014, at 11:42 PM, Anthony Alba  wrote:
> 
> > Is it time to update the SLURM FAQ entry?
> >
> > 1. SLURM 2.6.9 and 14.03 install pmi2 by default. (At least with the 
> > default RPM spec file).
> >
> > 2. 14.03.0 is also buggy wrt to pmi2.
> > It is fixed in 14.03 tip and soon 14.03.1 release.
> >
> >
> > - Anthony
> >
> > ___
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post: 
> > http://www.open-mpi.org/community/lists/devel/2014/04/14499.php
> 
> 
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/04/14528.php
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/04/14536.php


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

Re: [OMPI devel] 1-question developer poll

[Nathan Hjelm]

Git

On Wed, Apr 16, 2014 at 10:32:10AM +, Jeff Squyres (jsquyres) wrote:
> What source code repository technology(ies) do you use for Open MPI 
> development? (indicate all that apply)
> 
> - SVN
> - Mercurial
> - Git
> 
> I ask this question because there's serious discussions afoot to switch 
> OMPI's main SVN repo to Git, and I want to get a feel for the current 
> landscape out there.
> 
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/04/14537.php


pgpAU92flhwyQ.pgp
Description: PGP signature

Re: [OMPI devel] 1-question developer poll

[Dave Goodell (dgoodell)]

On Apr 16, 2014, at 5:32 AM, Jeff Squyres (jsquyres)  wrote:

> What source code repository technology(ies) do you use for Open MPI 
> development? (indicate all that apply)
> 
> - SVN
> - Mercurial
> - Git

Mostly Git (via the Github mirror and git-svn), and very rarely direct SVN.  
Never Mercurial.

-Dave

Re: [OMPI devel] Update SLURM FAQ entry?

[Ralph Castain]

Looks right to me as well - thanks!



On Wed, Apr 16, 2014 at 5:00 AM, Jeff Squyres (jsquyres)  wrote:

> Ralph -- does this text look ok to you?
>
> It looks ok to me.
>
>
> On Apr 15, 2014, at 9:52 PM, Anthony Alba  wrote:
>
> > Sure - how about this:
> >
> >
> > 2. Yes, if you have configured OMPI --with-pmi=foo, where foo is the
> path to the directory where pmi.h/pmi2.h is located. Slurm (> 2.6, > 14.03)
> installs PMI-2 support by default.
> >
> > Older versions of Slurm install PMI-1 by default. If you desire PMI-2,
> Slurm requires that you manually install that support. When the --with-pmi
> option is given, OMPI will automatically determine if PMI-2 support was
> built and use it in place of PMI-1.
> >
> > 4. Any issues with Slurm 2.6.3, 14.03?
> >
> > Yes. The Slurm 2.6.3, 14.03 releases have a bug in their PMI-2 support.
> >
> > For the slurm-2.6 branch,  it is recommended to use the latest version
> (2.6.9 as of 2014/4) which works with pmi2.
> >
> > For the slurm-14.03 branch, the fix will be in  14.03.1.
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Apr 15, 2014 at 9:46 PM, Jeff Squyres (jsquyres) <
> jsquy...@cisco.com> wrote:
> > Would you mind sending us updated text?  I don't know if any of us
> follows the SLURM releases closely...
> >
> > (I assume you're referring specifically to question 4, right?)
> >
> >
> >
> > On Apr 11, 2014, at 11:42 PM, Anthony Alba 
> wrote:
> >
> > > Is it time to update the SLURM FAQ entry?
> > >
> > > 1. SLURM 2.6.9 and 14.03 install pmi2 by default. (At least with the
> default RPM spec file).
> > >
> > > 2. 14.03.0 is also buggy wrt to pmi2.
> > > It is fixed in 14.03 tip and soon 14.03.1 release.
> > >
> > >
> > > - Anthony
> > >
> > > ___
> > > devel mailing list
> > > de...@open-mpi.org
> > > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > > Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/04/14499.php
> >
> >
> > --
> > Jeff Squyres
> > jsquy...@cisco.com
> > For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
> >
> > ___
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/04/14528.php
> >
> > ___
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/04/14536.php
>
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/04/14541.php
>

Re: [OMPI devel] Update SLURM FAQ entry?

[Jeff Squyres (jsquyres)]

Ralph -- does this text look ok to you?

It looks ok to me.


On Apr 15, 2014, at 9:52 PM, Anthony Alba  wrote:

> Sure - how about this:
> 
> 
> 2. Yes, if you have configured OMPI --with-pmi=foo, where foo is the path to 
> the directory where pmi.h/pmi2.h is located. Slurm (> 2.6, > 14.03) installs 
> PMI-2 support by default. 
> 
> Older versions of Slurm install PMI-1 by default. If you desire PMI-2, Slurm 
> requires that you manually install that support. When the --with-pmi option 
> is given, OMPI will automatically determine if PMI-2 support was built and 
> use it in place of PMI-1.
> 
> 4. Any issues with Slurm 2.6.3, 14.03?
> 
> Yes. The Slurm 2.6.3, 14.03 releases have a bug in their PMI-2 support. 
> 
> For the slurm-2.6 branch,  it is recommended to use the latest version (2.6.9 
> as of 2014/4) which works with pmi2.
> 
> For the slurm-14.03 branch, the fix will be in  14.03.1. 
> 
> 
> 
> 
> 
> 
> 
> On Tue, Apr 15, 2014 at 9:46 PM, Jeff Squyres (jsquyres)  
> wrote:
> Would you mind sending us updated text?  I don't know if any of us follows 
> the SLURM releases closely...
> 
> (I assume you're referring specifically to question 4, right?)
> 
> 
> 
> On Apr 11, 2014, at 11:42 PM, Anthony Alba  wrote:
> 
> > Is it time to update the SLURM FAQ entry?
> >
> > 1. SLURM 2.6.9 and 14.03 install pmi2 by default. (At least with the 
> > default RPM spec file).
> >
> > 2. 14.03.0 is also buggy wrt to pmi2.
> > It is fixed in 14.03 tip and soon 14.03.1 release.
> >
> >
> > - Anthony
> >
> > ___
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post: 
> > http://www.open-mpi.org/community/lists/devel/2014/04/14499.php
> 
> 
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/04/14528.php
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/04/14536.php


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

[OMPI devel] Bug in man page of MPI_Type_create_hindexed

[Bastian Beischer]

Dear all,

In open-mpi version 1.8 the man page of MPI_Type_create_hindexed gives this
declaration of the function:

int MPI_Type_create_hindexed(int count, const int array_of_blocklengths[],
const int array_of_displacements[], MPI_Datatype oldtype,
MPI_Datatype *newtype)

However I think the array_of_displacements should be of type MPI_Aint?

This was relevant to me because I wanted to create a datatype with large
offsets > INT_MAX and I didn't know I could use MPI_Type_create_hindexed
until a colleague pointed me to the MPI standard which says that the
displacements are of type MPI_Aint.

Cheers
Bastian

-- 
Bastian Beischer
RWTH Aachen University of Technology

@RWTH Aachen
Office: 28 C 203
Phone: +49-241-80-27205
E-mail: beisc...@physik.rwth-aachen.de
Address: I. Physikalisches Institut B, Sommerfeldstr. 14, D-52074 Aachen

@CERN
Office: Bdg 32-4-B12
Phone: +41-22-76-75750
E-mail: bastian.beisc...@cern.ch
Address: CERN, CH-1211 Geneve 23

Re: [OMPI devel] 1-question developer poll

[Ralph Castain]

Personally: svn and Mercurial

Intel uses git. However, we have had significant trouble keeping git repos
alive and clean in projects involving many developers that are
geographically dispersed. As a result, we've had to dedicate resources -
full-time people whose sole job is to maintain the git repos as it requires
someone with very high git knowledge to continually fix the problems. This
doesn't require one person/project, but it does require (a) significant
time, and (b) deep git knowledge.

The basic issue I'm hearing is the same we have surfaced before: git
exposes a lot of atomistic controls. This makes it very powerful, but also
very easy to make an error as it requires a high level of git-knowledge to
properly operate the system. Many developers lack that degree of "git IQ",
and don't take the time to learn it as they are under pressure to produce
actual code, or think they have it but don't know as much as they think. As
a result, the repo (main or the developer's branches) get confused and need
to be corrected.

Bottom line: so long as OMPI has at least one git-expert on the team who
can dedicate some of their time to helping developers "fix" their repo
problems, the proposed transition could be done. I'm not talking about
someone who will monitor/repair the main repo - I'm talking about someone
also willing to assist every member of the devel team when that person's
git branch gets hosed. If we ever lose that dedicated support, we may be in
trouble.

Unlike a corporation, we can't hire someone to fill this role. We rely on
contributed time from our members. So I think the question boils down to:
do we have that kind of commitment from our member organizations for the
foreseeable future? And should we adopt a technology that depends on that
contribution?

Ralph



On Wed, Apr 16, 2014 at 3:34 AM, Mike Dubman wrote:

> git
>
>
> On Wed, Apr 16, 2014 at 1:32 PM, Jeff Squyres (jsquyres) <
> jsquy...@cisco.com> wrote:
>
>> What source code repository technology(ies) do you use for Open MPI
>> development? (indicate all that apply)
>>
>> - SVN
>> - Mercurial
>> - Git
>>
>> I ask this question because there's serious discussions afoot to switch
>> OMPI's main SVN repo to Git, and I want to get a feel for the current
>> landscape out there.
>>
>> --
>> Jeff Squyres
>> jsquy...@cisco.com
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2014/04/14537.php
>>
>
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/04/14538.php
>

Re: [OMPI devel] 1-question developer poll

[Mike Dubman]

git


On Wed, Apr 16, 2014 at 1:32 PM, Jeff Squyres (jsquyres)  wrote:

> What source code repository technology(ies) do you use for Open MPI
> development? (indicate all that apply)
>
> - SVN
> - Mercurial
> - Git
>
> I ask this question because there's serious discussions afoot to switch
> OMPI's main SVN repo to Git, and I want to get a feel for the current
> landscape out there.
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/04/14537.php
>

[OMPI devel] 1-question developer poll

[Jeff Squyres (jsquyres)]

What source code repository technology(ies) do you use for Open MPI 
development? (indicate all that apply)

- SVN
- Mercurial
- Git

I ask this question because there's serious discussions afoot to switch OMPI's 
main SVN repo to Git, and I want to get a feel for the current landscape out 
there.

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