Re: [OMPI users] difference of behaviour for MPI_Publish_name between openmpi-1.4.5 and openmpi-1.8.4

2015-01-08 Thread Bernard Secher 

Thanks Gilles!

That works with this MPI_Info given to MPI_Publish_name.

Cheers,
Bernard

Le 08/01/2015 03:47, Gilles Gouaillardet a écrit :

Well, per the source code, this is not a bug but a feature :


from publish function from ompi/mca/pubsub/orte/pubsub_orte.c

 ompi_info_get_bool(info, "ompi_unique", , );
 if (0 == flag) {
 /* uniqueness not specified - overwrite by default */
 unique = false;
 }

fwiw, and at first glance, i would have expected the default behaviour
is to *not* overwrite (e.g. unique = true;).

anyway, in order to get the expected result, the user program can be
modified like this :

MPI_Info info;
MPI_Info_create();
MPI_Info_set(info, "ompi_unique", "true");

and then invoke MPI_Publish_name() with info instead of MPI_INFO_NULL

an updated version of the program

Cheers,

Gilles

On 2015/01/08 10:12, Ralph Castain wrote:

Hmmm…I confess this API gets little, if any, testing as it is so seldom used, 
so it is quite possible that a buglet has crept into it. I’ll take a look and 
try to have something in 1.8.5.

Thanks!
Ralph


On Jan 7, 2015, at 3:14 AM, Bernard Secher  wrote:

Hello,

With the version openmpi-1.4.5 I got an error  when I tried to publish the same 
name twice with the MPI_Publish_name routine
With the version openmpi-1.8.4 I got no error when I published the same name 
twice with the MPI_Publish_name routine

I used the attached script and source code to perform the test.

With this test, it works well with openmpi-1.4.5, but I get a deadlock with 
openmpi-1.8.4. I can suppress the deadlock with openmpi-1.8.4 if I modify the shell 
script and add a "sleep 1" command between the 2 mpirun commands.

Bernard
___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2015/01/26114.php

___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2015/01/26117.php



___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2015/01/26119.php



--
Logo CEA_
Bernard Sécher DEN/DM2S/STMF/LGLS
CEA Saclay, Bât 451, Pièce 32A
91191 Gif-sur-Yvette Cedex, France
bernard.sec...@cea.fr
Phone: 33 (0)1 69 08 73 78
Fax: 33 (0)1 69 08 10 87
_



Ce message électronique et tous les fichiers attachés qu'il contient 
sont confidentiels et destinés exclusivement à l'usage de la personne à 
laquelle ils sont adressés. Si vous avez reçu ce message par erreur, 
merci d'en avertir immédiatement son émetteur et de ne pas en conserver 
de copie.


This e-mail and any files transmitted with it are confidential and 
intended solely for the use of the individual to whom they are 
addressed. If you have received this e-mail in error please inform the 
sender immediately, without keeping any copy thereof.

Re: [OMPI users] difference of behaviour for MPI_Publish_name between openmpi-1.4.5 and openmpi-1.8.4

2015-01-07 Thread Ralph Castain 
Thanks!

> On Jan 7, 2015, at 6:56 PM, Gilles Gouaillardet 
>  wrote:
> 
> Ralph,
> 
> honestly, i do not know if the standard says anything
> (all i can do for now is blame the coin ;-) )
> 
> from now, i ll make a PR to update the man page (only master refers
> ompi_unique)
> 
> Cheers,
> 
> Gilles
> 
> commit 7d2e3028d608163247975397a09f30dbe7bd192a
> Author: Ralph Castain 
> Date:   Wed Aug 14 04:24:17 2013 +
> 
>Add unique info_key to documentation
> 
> On 2015/01/08 11:51, Ralph Castain wrote:
>> Does the standard say anything about the default behavior? IIRC, we set it 
>> this way because (a) we had no direction, and (b) it seemed just as 
>> reasonable as the alternative (I believe we flipped a coin)
>> 
>> 
>>> On Jan 7, 2015, at 6:47 PM, Gilles Gouaillardet 
>>>  wrote:
>>> 
>>> Well, per the source code, this is not a bug but a feature :
>>> 
>>> 
>>> from publish function from ompi/mca/pubsub/orte/pubsub_orte.c
>>> 
>>>   ompi_info_get_bool(info, "ompi_unique", , );
>>>   if (0 == flag) {
>>>   /* uniqueness not specified - overwrite by default */
>>>   unique = false;
>>>   }
>>> 
>>> fwiw, and at first glance, i would have expected the default behaviour
>>> is to *not* overwrite (e.g. unique = true;).
>>> 
>>> anyway, in order to get the expected result, the user program can be
>>> modified like this :
>>> 
>>> MPI_Info info;
>>> MPI_Info_create();
>>> MPI_Info_set(info, "ompi_unique", "true");
>>> 
>>> and then invoke MPI_Publish_name() with info instead of MPI_INFO_NULL
>>> 
>>> an updated version of the program
>>> 
>>> Cheers,
>>> 
>>> Gilles
>>> 
>>> On 2015/01/08 10:12, Ralph Castain wrote:
 Hmmm…I confess this API gets little, if any, testing as it is so seldom 
 used, so it is quite possible that a buglet has crept into it. I’ll take a 
 look and try to have something in 1.8.5.
 
 Thanks!
 Ralph
 
> On Jan 7, 2015, at 3:14 AM, Bernard Secher  wrote:
> 
> Hello,
> 
> With the version openmpi-1.4.5 I got an error  when I tried to publish 
> the same name twice with the MPI_Publish_name routine
> With the version openmpi-1.8.4 I got no error when I published the same 
> name twice with the MPI_Publish_name routine
> 
> I used the attached script and source code to perform the test.
> 
> With this test, it works well with openmpi-1.4.5, but I get a deadlock 
> with openmpi-1.8.4. I can suppress the deadlock with openmpi-1.8.4 if I 
> modify the shell script and add a "sleep 1" command between the 2 mpirun 
> commands.
> 
> Bernard
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/01/26114.php
 ___
 users mailing list
 us...@open-mpi.org
 Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
 Link to this post: 
 http://www.open-mpi.org/community/lists/users/2015/01/26117.php
>>> ___
>>> users mailing list
>>> us...@open-mpi.org
>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>>> Link to this post: 
>>> http://www.open-mpi.org/community/lists/users/2015/01/26119.php
>> ___
>> users mailing list
>> us...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/users/2015/01/26120.php
> 
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/01/26121.php

Re: [OMPI users] difference of behaviour for MPI_Publish_name between openmpi-1.4.5 and openmpi-1.8.4

2015-01-07 Thread Gilles Gouaillardet 
Ralph,

honestly, i do not know if the standard says anything
(all i can do for now is blame the coin ;-) )

from now, i ll make a PR to update the man page (only master refers
ompi_unique)

Cheers,

Gilles

commit 7d2e3028d608163247975397a09f30dbe7bd192a
Author: Ralph Castain 
List-Post: users@lists.open-mpi.org
Date:   Wed Aug 14 04:24:17 2013 +

Add unique info_key to documentation

On 2015/01/08 11:51, Ralph Castain wrote:
> Does the standard say anything about the default behavior? IIRC, we set it 
> this way because (a) we had no direction, and (b) it seemed just as 
> reasonable as the alternative (I believe we flipped a coin)
>
>
>> On Jan 7, 2015, at 6:47 PM, Gilles Gouaillardet 
>>  wrote:
>>
>> Well, per the source code, this is not a bug but a feature :
>>
>>
>> from publish function from ompi/mca/pubsub/orte/pubsub_orte.c
>>
>>ompi_info_get_bool(info, "ompi_unique", , );
>>if (0 == flag) {
>>/* uniqueness not specified - overwrite by default */
>>unique = false;
>>}
>>
>> fwiw, and at first glance, i would have expected the default behaviour
>> is to *not* overwrite (e.g. unique = true;).
>>
>> anyway, in order to get the expected result, the user program can be
>> modified like this :
>>
>> MPI_Info info;
>> MPI_Info_create();
>> MPI_Info_set(info, "ompi_unique", "true");
>>
>> and then invoke MPI_Publish_name() with info instead of MPI_INFO_NULL
>>
>> an updated version of the program
>>
>> Cheers,
>>
>> Gilles
>>
>> On 2015/01/08 10:12, Ralph Castain wrote:
>>> Hmmm…I confess this API gets little, if any, testing as it is so seldom 
>>> used, so it is quite possible that a buglet has crept into it. I’ll take a 
>>> look and try to have something in 1.8.5.
>>>
>>> Thanks!
>>> Ralph
>>>
 On Jan 7, 2015, at 3:14 AM, Bernard Secher  wrote:

 Hello,

 With the version openmpi-1.4.5 I got an error  when I tried to publish the 
 same name twice with the MPI_Publish_name routine
 With the version openmpi-1.8.4 I got no error when I published the same 
 name twice with the MPI_Publish_name routine

 I used the attached script and source code to perform the test.

 With this test, it works well with openmpi-1.4.5, but I get a deadlock 
 with openmpi-1.8.4. I can suppress the deadlock with openmpi-1.8.4 if I 
 modify the shell script and add a "sleep 1" command between the 2 mpirun 
 commands.

 Bernard
 ___
 users mailing list
 us...@open-mpi.org
 Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
 Link to this post: 
 http://www.open-mpi.org/community/lists/users/2015/01/26114.php
>>> ___
>>> users mailing list
>>> us...@open-mpi.org
>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>>> Link to this post: 
>>> http://www.open-mpi.org/community/lists/users/2015/01/26117.php
>> ___
>> users mailing list
>> us...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/users/2015/01/26119.php
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/01/26120.php

Re: [OMPI users] difference of behaviour for MPI_Publish_name between openmpi-1.4.5 and openmpi-1.8.4

2015-01-07 Thread Ralph Castain 
Does the standard say anything about the default behavior? IIRC, we set it this 
way because (a) we had no direction, and (b) it seemed just as reasonable as 
the alternative (I believe we flipped a coin)


> On Jan 7, 2015, at 6:47 PM, Gilles Gouaillardet 
>  wrote:
> 
> Well, per the source code, this is not a bug but a feature :
> 
> 
> from publish function from ompi/mca/pubsub/orte/pubsub_orte.c
> 
>ompi_info_get_bool(info, "ompi_unique", , );
>if (0 == flag) {
>/* uniqueness not specified - overwrite by default */
>unique = false;
>}
> 
> fwiw, and at first glance, i would have expected the default behaviour
> is to *not* overwrite (e.g. unique = true;).
> 
> anyway, in order to get the expected result, the user program can be
> modified like this :
> 
> MPI_Info info;
> MPI_Info_create();
> MPI_Info_set(info, "ompi_unique", "true");
> 
> and then invoke MPI_Publish_name() with info instead of MPI_INFO_NULL
> 
> an updated version of the program
> 
> Cheers,
> 
> Gilles
> 
> On 2015/01/08 10:12, Ralph Castain wrote:
>> Hmmm…I confess this API gets little, if any, testing as it is so seldom 
>> used, so it is quite possible that a buglet has crept into it. I’ll take a 
>> look and try to have something in 1.8.5.
>> 
>> Thanks!
>> Ralph
>> 
>>> On Jan 7, 2015, at 3:14 AM, Bernard Secher  wrote:
>>> 
>>> Hello,
>>> 
>>> With the version openmpi-1.4.5 I got an error  when I tried to publish the 
>>> same name twice with the MPI_Publish_name routine
>>> With the version openmpi-1.8.4 I got no error when I published the same 
>>> name twice with the MPI_Publish_name routine
>>> 
>>> I used the attached script and source code to perform the test.
>>> 
>>> With this test, it works well with openmpi-1.4.5, but I get a deadlock with 
>>> openmpi-1.8.4. I can suppress the deadlock with openmpi-1.8.4 if I modify 
>>> the shell script and add a "sleep 1" command between the 2 mpirun commands.
>>> 
>>> Bernard
>>> ___
>>> users mailing list
>>> us...@open-mpi.org
>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>>> Link to this post: 
>>> http://www.open-mpi.org/community/lists/users/2015/01/26114.php
>> ___
>> users mailing list
>> us...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/users/2015/01/26117.php
> 
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/01/26119.php

Re: [OMPI users] difference of behaviour for MPI_Publish_name between openmpi-1.4.5 and openmpi-1.8.4

2015-01-07 Thread Gilles Gouaillardet 
Well, per the source code, this is not a bug but a feature :


from publish function from ompi/mca/pubsub/orte/pubsub_orte.c

ompi_info_get_bool(info, "ompi_unique", , );
if (0 == flag) {
/* uniqueness not specified - overwrite by default */
unique = false;
}

fwiw, and at first glance, i would have expected the default behaviour
is to *not* overwrite (e.g. unique = true;).

anyway, in order to get the expected result, the user program can be
modified like this :

MPI_Info info;
MPI_Info_create();
MPI_Info_set(info, "ompi_unique", "true");

and then invoke MPI_Publish_name() with info instead of MPI_INFO_NULL

an updated version of the program

Cheers,

Gilles

On 2015/01/08 10:12, Ralph Castain wrote:
> Hmmm…I confess this API gets little, if any, testing as it is so seldom used, 
> so it is quite possible that a buglet has crept into it. I’ll take a look and 
> try to have something in 1.8.5.
>
> Thanks!
> Ralph
>
>> On Jan 7, 2015, at 3:14 AM, Bernard Secher  wrote:
>>
>> Hello,
>>
>> With the version openmpi-1.4.5 I got an error  when I tried to publish the 
>> same name twice with the MPI_Publish_name routine
>> With the version openmpi-1.8.4 I got no error when I published the same name 
>> twice with the MPI_Publish_name routine
>>
>> I used the attached script and source code to perform the test.
>>
>> With this test, it works well with openmpi-1.4.5, but I get a deadlock with 
>> openmpi-1.8.4. I can suppress the deadlock with openmpi-1.8.4 if I modify 
>> the shell script and add a "sleep 1" command between the 2 mpirun commands.
>>
>> Bernard
>> ___
>> users mailing list
>> us...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/users/2015/01/26114.php
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/01/26117.php

// Copyright (C) 2011-2014  CEA/DEN, EDF R, OPEN CASCADE
//
// This library is free software; you can redistribute it and/or
// modify it under the terms of the GNU Lesser General Public
// License as published by the Free Software Foundation; either
// version 2.1 of the License, or (at your option) any later version.
//
// This library is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
// Lesser General Public License for more details.
//
// You should have received a copy of the GNU Lesser General Public
// License along with this library; if not, write to the Free Software
// Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307 USA
//
// See http://www.salome-platform.org/ or email : 
webmaster.sal...@opencascade.com
//

#include 
#include 
#include 
#include 
#define TIMEOUT 20
#define EPSILON 0.0001

#ifndef WIN32
# include 
#endif

int main(int argc, char**argv)
{
  int *indg;
  double *vector, sum=0., norm, etalon;
  int rank, size, grank, gsize, rsize;
  int vsize=20, lvsize, rlvsize;
  int i, k1, k2, imin, imax, nb;
  int srv=0;
  MPI_Comm com, icom;
  MPI_Status status; 
  MPI_Info info;
  char   port_name [MPI_MAX_PORT_NAME]; 
  char   port_name_clt [MPI_MAX_PORT_NAME]; 
  std::string service = "SERVICE";
  bool debug=false;

#ifndef OPEN_MPI
  std::cout << "This test only works with openmpi implementation" << std::endl;
  exit(1);
#endif

  for(i=1;i

Re: [OMPI users] difference of behaviour for MPI_Publish_name between openmpi-1.4.5 and openmpi-1.8.4

2015-01-07 Thread Ralph Castain 
Hmmm…I confess this API gets little, if any, testing as it is so seldom used, 
so it is quite possible that a buglet has crept into it. I’ll take a look and 
try to have something in 1.8.5.

Thanks!
Ralph

> On Jan 7, 2015, at 3:14 AM, Bernard Secher  wrote:
> 
> Hello,
> 
> With the version openmpi-1.4.5 I got an error  when I tried to publish the 
> same name twice with the MPI_Publish_name routine
> With the version openmpi-1.8.4 I got no error when I published the same name 
> twice with the MPI_Publish_name routine
> 
> I used the attached script and source code to perform the test.
> 
> With this test, it works well with openmpi-1.4.5, but I get a deadlock with 
> openmpi-1.8.4. I can suppress the deadlock with openmpi-1.8.4 if I modify the 
> shell script and add a "sleep 1" command between the 2 mpirun commands.
> 
> Bernard
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/01/26114.php

[OMPI users] difference of behaviour for MPI_Publish_name between openmpi-1.4.5 and openmpi-1.8.4

2015-01-07 Thread Bernard Secher 

Hello,

With the version openmpi-1.4.5 I got an error  when I tried to publish 
the same name twice with the MPI_Publish_name routine
With the version openmpi-1.8.4 I got no error when I published the same 
name twice with the MPI_Publish_name routine


I used the attached script and source code to perform the test.

With this test, it works well with openmpi-1.4.5, but I get a deadlock 
with openmpi-1.8.4. I can suppress the deadlock with openmpi-1.8.4 if I 
modify the shell script and add a "sleep 1" command between the 2 mpirun 
commands.


Bernard
// Copyright (C) 2011-2014  CEA/DEN, EDF R, OPEN CASCADE
//
// This library is free software; you can redistribute it and/or
// modify it under the terms of the GNU Lesser General Public
// License as published by the Free Software Foundation; either
// version 2.1 of the License, or (at your option) any later version.
//
// This library is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
// Lesser General Public License for more details.
//
// You should have received a copy of the GNU Lesser General Public
// License along with this library; if not, write to the Free Software
// Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307 USA
//
// See http://www.salome-platform.org/ or email : webmaster.sal...@opencascade.com
//

#include 
#include 
#include 
#include 
#define TIMEOUT 20
#define EPSILON 0.0001

#ifndef WIN32
# include 
#endif

int main(int argc, char**argv)
{
  int *indg;
  double *vector, sum=0., norm, etalon;
  int rank, size, grank, gsize, rsize;
  int vsize=20, lvsize, rlvsize;
  int i, k1, k2, imin, imax, nb;
  int srv=0;
  MPI_Comm com, icom;
  MPI_Status status; 
  char   port_name [MPI_MAX_PORT_NAME]; 
  char   port_name_clt [MPI_MAX_PORT_NAME]; 
  std::string service = "SERVICE";
  bool debug=false;

#ifndef OPEN_MPI
  std::cout << "This test only works with openmpi implementation" << std::endl;
  exit(1);
#endif

  for(i=1;i
    
    
7 matches