Re: [OMPI devel] Migration of mailman mailing lists

[Jeff Squyres (jsquyres)]

On Jul 18, 2016, at 9:46 PM, Christopher Samuel  wrote:
> 
>> Yes, kill all netloc lists.
> 
> Will the archives be preserved somewhere for historical reference?

The plan is to preserve the list archives as they exist right now, even if we 
don't migrate the list.

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

Re: [OMPI devel] Migration of mailman mailing lists

[Christopher Samuel]

On 19/07/16 02:05, Brice Goglin wrote:

> Yes, kill all netloc lists.

Will the archives be preserved somewhere for historical reference?

All the best,
Chris
-- 
 Christopher SamuelSenior Systems Administrator
 VLSCI - Victorian Life Sciences Computation Initiative
 Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545
 http://www.vlsci.org.au/  http://twitter.com/vlsci

[OMPI devel] tcp btl rendezvous performance question

[Howard Pritchard]

Hi Folks,

I have a cluster with some 100 Gb ethernet cards
installed.  What we are noticing if we force Open MPI 1.10.3
to go through the TCP BTL (rather than yalla)  is that
the performance of osu_bw once the TCP BTL switches
from eager to rendezvous (> 32KB)
falls off a cliff, going from about 1.6 GB/sec to 233 MB/sec
and stays that way out to 4 MB message lengths.

There's nothing wrong with the IP stack (iperf -P4 gives
63 Gb/sec).

So, my questions are

1) is this performance expected for the TCP BTL when in
rendezvous mode?
2) is there some way to get more like the single socket
performance obtained with iperf for large messages (~16 Gb/sec).

We tried adjusting the tcp_btl_rendezvous threshold but that doesn't
appear to actually be adjustable from the mpirun command line.

Thanks for any suggestions,

Howard

Re: [OMPI devel] Change compiler

[Paul Hargrove]

Murali,

I typically configure with
   CC=clang CXX=clang++
on the configure command line.
Editing of the files generated by configure (such as the Makefile) is not
advisable.

-Paul

On Mon, Jul 18, 2016 at 1:06 PM, Emani, Murali  wrote:

> Hi all,
>
> I would like to know if there is Clang support for OpenMPI codebase.
>
> I am trying to change the underlying compiler from gcc to clang in
> ‘configure' and ‘make all install’, I changed these values in Makefile in
> root dir and another one in config directory. The steps during ‘configure’
> reflect gcc again instead of clang. Is this the right way or am I missing
> something here ?
>
> Is the wrapper compiler environment variable ‘OMPI_CC’ intended to replace
> the underlying compiler when compiling an MPI application.
>
>
> —
> Murali
>
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2016/07/19235.php
>



-- 
Paul H. Hargrove  phhargr...@lbl.gov
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900

Re: [OMPI devel] Migration of mailman mailing lists

[Jeff Squyres (jsquyres)]

Roger.

> On Jul 18, 2016, at 12:05 PM, Brice Goglin  wrote:
> 
> Yes, kill all netloc lists.
> Brice
> 
> 
> Le 18 juillet 2016 17:43:49 UTC+02:00, Josh Hursey  a 
> écrit :
> Now that netloc has rolled into hwloc, I think it is safe to kill the netloc 
> lists.
> 
> mtt-devel-core and mtt-annouce should be kept. They probably need to be 
> cleaned. But the hope is that we release MTT at some point in the near-ish 
> future.
> 
> On Mon, Jul 18, 2016 at 10:20 AM, Jeff Squyres (jsquyres) 
>  wrote:
> We're progressing in the migration plans.  Next up is the mailing lists.  The 
> first step is to determine which lists to migrate, and which to delete 
> (because they're now no longer necessary, anyway).
> 
> These are the lists we plan to keep/migrate, and the lists we plan to 
> delete/not migrate -- if you know of any list we mis-classified, please let 
> us know ASAP.  We plan to start this migration as early as Tuesday afternoon.
> 
> Lists that we want to keep:
> • Admin
> • Announce
> • Devel
> • Devel-core
> • Hwloc-announce
> • Hwloc-commits -- gitdub sends to this list; KEEP
> • Hwloc-devel
> • Hwloc-users
> • Mirrors
> • Mtt-commits
> • Mtt-devel
> • Mtt-results -- daily MTT results sent to this list; KEEP
> • Mtt-users
> • Ompi-commits -- gitdub sends to this list; KEEP
> • Users
> 
> Lists that we know that we do not want to migrate:
> • Bugs -- Trac used to send to this list; it’s now moot and can be killed.
> • Docs -- kill?
> • mtt-announce -- kill?
> • mtt-devel-core -- kill?
> • Netloc-announce -- kill?
> • Netloc-bugs -- kill?
> • Netloc-commits -- kill?
> • Netloc-devel -- kill?
> • Netloc-users -- kill?
> • ompi-user-docs-bugs -- kill?
> • ompi-user-docs-svn -- kill?
> • otpo-bugs -- kill?
> • otpo-svn -- kill?
> • otpo-users -- kill?
> • Any glassbottom list
> • Any orcm list
> • Any pmix list
> 
> --
> 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: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2016/07/19231.php
> 
> 
> 
> devel mailing list
> de...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2016/07/19232.php
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2016/07/19233.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] Migration of mailman mailing lists

[Brice Goglin]

Yes, kill all netloc lists.
Brice


Le 18 juillet 2016 17:43:49 UTC+02:00, Josh Hursey  a 
écrit :
>Now that netloc has rolled into hwloc, I think it is safe to kill the
>netloc lists.
>
>mtt-devel-core and mtt-annouce should be kept. They probably need to be
>cleaned. But the hope is that we release MTT at some point in the
>near-ish
>future.
>
>On Mon, Jul 18, 2016 at 10:20 AM, Jeff Squyres (jsquyres) <
>jsquy...@cisco.com> wrote:
>
>> We're progressing in the migration plans.  Next up is the mailing
>lists.
>> The first step is to determine which lists to migrate, and which to
>delete
>> (because they're now no longer necessary, anyway).
>>
>> These are the lists we plan to keep/migrate, and the lists we plan to
>> delete/not migrate -- if you know of any list we mis-classified,
>please let
>> us know ASAP.  We plan to start this migration as early as Tuesday
>> afternoon.
>>
>> Lists that we want to keep:
>> • Admin
>> • Announce
>> • Devel
>> • Devel-core
>> • Hwloc-announce
>> • Hwloc-commits -- gitdub sends to this list; KEEP
>> • Hwloc-devel
>> • Hwloc-users
>> • Mirrors
>> • Mtt-commits
>> • Mtt-devel
>> • Mtt-results -- daily MTT results sent to this list; KEEP
>> • Mtt-users
>> • Ompi-commits -- gitdub sends to this list; KEEP
>> • Users
>>
>> Lists that we know that we do not want to migrate:
>> • Bugs -- Trac used to send to this list; it’s now moot and can be
>killed.
>> • Docs -- kill?
>> • mtt-announce -- kill?
>> • mtt-devel-core -- kill?
>> • Netloc-announce -- kill?
>> • Netloc-bugs -- kill?
>> • Netloc-commits -- kill?
>> • Netloc-devel -- kill?
>> • Netloc-users -- kill?
>> • ompi-user-docs-bugs -- kill?
>> • ompi-user-docs-svn -- kill?
>> • otpo-bugs -- kill?
>> • otpo-svn -- kill?
>> • otpo-users -- kill?
>> • Any glassbottom list
>> • Any orcm list
>> • Any pmix list
>>
>> --
>> 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: https://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2016/07/19231.php
>
>
>
>
>___
>devel mailing list
>de...@open-mpi.org
>Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
>Link to this post:
>http://www.open-mpi.org/community/lists/devel/2016/07/19232.php

Re: [OMPI devel] Migration of mailman mailing lists

[Josh Hursey]

Now that netloc has rolled into hwloc, I think it is safe to kill the
netloc lists.

mtt-devel-core and mtt-annouce should be kept. They probably need to be
cleaned. But the hope is that we release MTT at some point in the near-ish
future.

On Mon, Jul 18, 2016 at 10:20 AM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:

> We're progressing in the migration plans.  Next up is the mailing lists.
> The first step is to determine which lists to migrate, and which to delete
> (because they're now no longer necessary, anyway).
>
> These are the lists we plan to keep/migrate, and the lists we plan to
> delete/not migrate -- if you know of any list we mis-classified, please let
> us know ASAP.  We plan to start this migration as early as Tuesday
> afternoon.
>
> Lists that we want to keep:
> • Admin
> • Announce
> • Devel
> • Devel-core
> • Hwloc-announce
> • Hwloc-commits -- gitdub sends to this list; KEEP
> • Hwloc-devel
> • Hwloc-users
> • Mirrors
> • Mtt-commits
> • Mtt-devel
> • Mtt-results -- daily MTT results sent to this list; KEEP
> • Mtt-users
> • Ompi-commits -- gitdub sends to this list; KEEP
> • Users
>
> Lists that we know that we do not want to migrate:
> • Bugs -- Trac used to send to this list; it’s now moot and can be killed.
> • Docs -- kill?
> • mtt-announce -- kill?
> • mtt-devel-core -- kill?
> • Netloc-announce -- kill?
> • Netloc-bugs -- kill?
> • Netloc-commits -- kill?
> • Netloc-devel -- kill?
> • Netloc-users -- kill?
> • ompi-user-docs-bugs -- kill?
> • ompi-user-docs-svn -- kill?
> • otpo-bugs -- kill?
> • otpo-svn -- kill?
> • otpo-users -- kill?
> • Any glassbottom list
> • Any orcm list
> • Any pmix list
>
> --
> 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: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2016/07/19231.php

[OMPI devel] Migration of mailman mailing lists

[Jeff Squyres (jsquyres)]

We're progressing in the migration plans.  Next up is the mailing lists.  The 
first step is to determine which lists to migrate, and which to delete (because 
they're now no longer necessary, anyway).

These are the lists we plan to keep/migrate, and the lists we plan to 
delete/not migrate -- if you know of any list we mis-classified, please let us 
know ASAP.  We plan to start this migration as early as Tuesday afternoon.

Lists that we want to keep:
• Admin
• Announce
• Devel
• Devel-core
• Hwloc-announce
• Hwloc-commits -- gitdub sends to this list; KEEP
• Hwloc-devel
• Hwloc-users
• Mirrors
• Mtt-commits
• Mtt-devel
• Mtt-results -- daily MTT results sent to this list; KEEP
• Mtt-users
• Ompi-commits -- gitdub sends to this list; KEEP
• Users

Lists that we know that we do not want to migrate:
• Bugs -- Trac used to send to this list; it’s now moot and can be killed.
• Docs -- kill?
• mtt-announce -- kill?
• mtt-devel-core -- kill?
• Netloc-announce -- kill?
• Netloc-bugs -- kill?
• Netloc-commits -- kill?
• Netloc-devel -- kill?
• Netloc-users -- kill?
• ompi-user-docs-bugs -- kill?
• ompi-user-docs-svn -- kill?
• otpo-bugs -- kill?
• otpo-svn -- kill?
• otpo-users -- kill?
• Any glassbottom list
• Any orcm list
• Any pmix list

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

Re: [OMPI devel] OSHMEM out-of-date?

[Ralph Castain]

Sorry - this is on today’s master

> On Jul 17, 2016, at 8:31 PM, Artem Polyakov  wrote:
> 
> What is it? What repository?
> 
> понедельник, 18 июля 2016 г. пользователь Ralph Castain написал:
> In file included from 
> ../../../../oshmem/shmem/fortran/prototypes_shmem.h:14:0,
>  from ../../../../oshmem/shmem/fortran/bindings.h:15,
>  from pshmem_put_f.c:13:
> pshmem_put_f.c: In function ‘shmem_put_f’:
> ../../../../oshmem/shmem/fortran/shmem_fortran_pointer.h:15:28: warning: 
> passing argument 2 of ‘mca_spml.spml_put’ makes integer from pointer without 
> a cast [-Wint-conversion]
>  #define FPTR_2_VOID_PTR(a) ((void *)(a))
> ^
> ../../../../oshmem/mca/spml/spml.h:329:44: note: in expansion of macro 
> ‘FPTR_2_VOID_PTR’
>  #define MCA_SPML_CALL(a) mca_spml.spml_ ## a
> ^
> pshmem_put_f.c:36:5: note: in expansion of macro ‘MCA_SPML_CALL’
>  MCA_SPML_CALL(put(FPTR_2_VOID_PTR(target),
>  ^
> ../../../../oshmem/shmem/fortran/shmem_fortran_pointer.h:15:28: note: 
> expected ‘size_t {aka long unsigned int}’ but argument is of type ‘void *’
>  #define FPTR_2_VOID_PTR(a) ((void *)(a))
> ^
> ../../../../oshmem/mca/spml/spml.h:329:44: note: in expansion of macro 
> ‘FPTR_2_VOID_PTR’
>  #define MCA_SPML_CALL(a) mca_spml.spml_ ## a
> ^
> pshmem_put_f.c:36:5: note: in expansion of macro ‘MCA_SPML_CALL’
>  MCA_SPML_CALL(put(FPTR_2_VOID_PTR(target),
>  ^
> In file included from ../../../../oshmem/shmem/fortran/bindings.h:16:0,
>  from pshmem_put_f.c:13:
> pshmem_put_f.c:38:25: warning: passing argument 3 of ‘mca_spml.spml_put’ 
> makes pointer from integer without a cast [-Wint-conversion]
>  OMPI_FINT_2_INT(*length),
>  ^
> ../../../../ompi/mpi/fortran/base/fint_2_int.h:41:30: note: in definition of 
> macro ‘OMPI_FINT_2_INT’
>#define OMPI_FINT_2_INT(a) a
>   ^
> pshmem_put_f.c:36:5: note: in expansion of macro ‘MCA_SPML_CALL’
>  MCA_SPML_CALL(put(FPTR_2_VOID_PTR(target),
>  ^
> pshmem_put_f.c:38:25: note: expected ‘void *’ but argument is of type ‘int’
>  OMPI_FINT_2_INT(*length),
>  ^
> ../../../../ompi/mpi/fortran/base/fint_2_int.h:41:30: note: in definition of 
> macro ‘OMPI_FINT_2_INT’
>#define OMPI_FINT_2_INT(a) a
>   ^
> pshmem_put_f.c:36:5: note: in expansion of macro ‘MCA_SPML_CALL’
>  MCA_SPML_CALL(put(FPTR_2_VOID_PTR(target),
> 
> 
> 
> 
> 
> -- 
> -
> Best regards, Artem Polyakov
> (Mobile mail)
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2016/07/19228.php

Re: [OMPI devel] OSHMEM out-of-date?

[Artem Polyakov]

What is it? What repository?

понедельник, 18 июля 2016 г. пользователь Ralph Castain написал:

> In file included from
> *../../../../oshmem/shmem/fortran/prototypes_shmem.h:14:0*,
>  from *../../../../oshmem/shmem/fortran/bindings.h:15*,
>  from *pshmem_put_f.c:13*:
> *pshmem_put_f.c:* In function ‘*shmem_put_f*’:
> *../../../../oshmem/shmem/fortran/shmem_fortran_pointer.h:15:28:* *warning:
> *passing argument 2 of ‘*mca_spml.spml_put*’ makes integer from pointer
> without a cast [*-Wint-conversion*]
>  #define FPTR_2_VOID_PTR(a) *(*(void *)(a))
> *^*
> *../../../../oshmem/mca/spml/spml.h:329:44:* *note: *in expansion of
> macro ‘*FPTR_2_VOID_PTR*’
>  #define MCA_SPML_CALL(a) mca_spml.spml_ ## *a*
> *^*
> *pshmem_put_f.c:36:5:* *note: *in expansion of macro ‘*MCA_SPML_CALL*’
>  *MCA_SPML_CALL*(put(FPTR_2_VOID_PTR(target),
>  *^*
> *../../../../oshmem/shmem/fortran/shmem_fortran_pointer.h:15:28:* *note: 
> *expected
> ‘*size_t {aka long unsigned int}*’ but argument is of type ‘*void **’
>  #define FPTR_2_VOID_PTR(a) *(*(void *)(a))
> *^*
> *../../../../oshmem/mca/spml/spml.h:329:44:* *note: *in expansion of
> macro ‘*FPTR_2_VOID_PTR*’
>  #define MCA_SPML_CALL(a) mca_spml.spml_ ## *a*
> *^*
> *pshmem_put_f.c:36:5:* *note: *in expansion of macro ‘*MCA_SPML_CALL*’
>  *MCA_SPML_CALL*(put(FPTR_2_VOID_PTR(target),
>  *^*
> In file included from *../../../../oshmem/shmem/fortran/bindings.h:16:0*,
>  from *pshmem_put_f.c:13*:
> *pshmem_put_f.c:38:25:* *warning: *passing argument 3 of ‘
> *mca_spml.spml_put*’ makes pointer from integer without a cast [
> *-Wint-conversion*]
>  OMPI_FINT_2_INT(***length),
>  *^*
> *../../../../ompi/mpi/fortran/base/fint_2_int.h:41:30:* *note: *in
> definition of macro ‘*OMPI_FINT_2_INT*’
>#define OMPI_FINT_2_INT(a) *a*
>   *^*
> *pshmem_put_f.c:36:5:* *note: *in expansion of macro ‘*MCA_SPML_CALL*’
>  *MCA_SPML_CALL*(put(FPTR_2_VOID_PTR(target),
>  *^*
> *pshmem_put_f.c:38:25:* *note: *expected ‘*void **’ but argument is of
> type ‘*int*’
>  OMPI_FINT_2_INT(***length),
>  *^*
> *../../../../ompi/mpi/fortran/base/fint_2_int.h:41:30:* *note: *in
> definition of macro ‘*OMPI_FINT_2_INT*’
>#define OMPI_FINT_2_INT(a) *a*
>   *^*
> *pshmem_put_f.c:36:5:* *note: *in expansion of macro ‘*MCA_SPML_CALL*’
>  *MCA_SPML_CALL*(put(FPTR_2_VOID_PTR(target),
>
>
>
>

-- 
-
Best regards, Artem Polyakov
(Mobile mail)

[OMPI devel] OSHMEM out-of-date?

[Ralph Castain]

In file included from ../../../../oshmem/shmem/fortran/prototypes_shmem.h:14:0,
 from ../../../../oshmem/shmem/fortran/bindings.h:15,
 from pshmem_put_f.c:13:
pshmem_put_f.c: In function ‘shmem_put_f’:
../../../../oshmem/shmem/fortran/shmem_fortran_pointer.h:15:28: warning: 
passing argument 2 of ‘mca_spml.spml_put’ makes integer from pointer without a 
cast [-Wint-conversion]
 #define FPTR_2_VOID_PTR(a) ((void *)(a))
^
../../../../oshmem/mca/spml/spml.h:329:44: note: in expansion of macro 
‘FPTR_2_VOID_PTR’
 #define MCA_SPML_CALL(a) mca_spml.spml_ ## a
^
pshmem_put_f.c:36:5: note: in expansion of macro ‘MCA_SPML_CALL’
 MCA_SPML_CALL(put(FPTR_2_VOID_PTR(target),
 ^
../../../../oshmem/shmem/fortran/shmem_fortran_pointer.h:15:28: note: expected 
‘size_t {aka long unsigned int}’ but argument is of type ‘void *’
 #define FPTR_2_VOID_PTR(a) ((void *)(a))
^
../../../../oshmem/mca/spml/spml.h:329:44: note: in expansion of macro 
‘FPTR_2_VOID_PTR’
 #define MCA_SPML_CALL(a) mca_spml.spml_ ## a
^
pshmem_put_f.c:36:5: note: in expansion of macro ‘MCA_SPML_CALL’
 MCA_SPML_CALL(put(FPTR_2_VOID_PTR(target),
 ^
In file included from ../../../../oshmem/shmem/fortran/bindings.h:16:0,
 from pshmem_put_f.c:13:
pshmem_put_f.c:38:25: warning: passing argument 3 of ‘mca_spml.spml_put’ makes 
pointer from integer without a cast [-Wint-conversion]
 OMPI_FINT_2_INT(*length),
 ^
../../../../ompi/mpi/fortran/base/fint_2_int.h:41:30: note: in definition of 
macro ‘OMPI_FINT_2_INT’
   #define OMPI_FINT_2_INT(a) a
  ^
pshmem_put_f.c:36:5: note: in expansion of macro ‘MCA_SPML_CALL’
 MCA_SPML_CALL(put(FPTR_2_VOID_PTR(target),
 ^
pshmem_put_f.c:38:25: note: expected ‘void *’ but argument is of type ‘int’
 OMPI_FINT_2_INT(*length),
 ^
../../../../ompi/mpi/fortran/base/fint_2_int.h:41:30: note: in definition of 
macro ‘OMPI_FINT_2_INT’
   #define OMPI_FINT_2_INT(a) a
  ^
pshmem_put_f.c:36:5: note: in expansion of macro ‘MCA_SPML_CALL’
 MCA_SPML_CALL(put(FPTR_2_VOID_PTR(target),