Re: [OMPI devel] [OMPI svn] svn:open-mpi r31302 - in trunk: opal/mca/base orte/tools/orterun

[Mike Dubman]

mca param file treats any key=val as mca parameter only.
In order to add parser support for something that is not mca param, will
require change file syntax and it will look bad, i.e.:

mca btl = sm,self,openib
env DISPLAY = console:0

I think the current implementation is less intrusive and re-uses existing
infra in the most elegant way.
The param file syntax change is too big effort to justify this feature
(IMHO) which can be provided with existing infra w/o breaking anything.



On Wed, Apr 2, 2014 at 3:04 AM, Ralph Castain  wrote:

> Understood - my point, however, was that we can easily add that capability
> to the mca params file.. This would seem far preferable to creating a
> completely new, parallel way of setting envars.
>
> Why not do it that way?
>
>
>
> On Tue, Apr 1, 2014 at 4:34 PM, Mike Dubman wrote:
>
>> The "-x var=val" cannot be placed into mca params file.
>>
>>
>> On Wed, Apr 2, 2014 at 2:34 AM, Mike Dubman wrote:
>>
>>> yes, it is expected that the "string" value should be quoted. will
>>> clarify it in the help message and man page. Thanks for spotting.
>>>
>>> The underlying libraries used from OMPI
>>> (mxm,psm,hcoll,glibc,pmi2,slurm,...) all have shell environment variables
>>> to control their behave.
>>>
>>> It is unreasonable to expose mca parameter for every library tunable
>>> used from ompi, but for most frequently used ones.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Apr 2, 2014 at 2:23 AM, Ralph Castain  wrote:
>>>
 If you are expecting the user to put quotes around the string, then you
 better tell them that in the help message. Otherwise, they would do what I
 did - simply list the envars with a space in-between, and everything fails.

 Also, you need to update mpirun.1in to reflect this new option or else
 nobody will know about it :-)

 However, looking at your example leaves me totally puzzled. Why are
 these not just MCA params to begin with, in which case we don't need
 another duplicate mechanism for setting them?

 We should only be setting envars that have nothing to do with OMPI, not
 setting OMPI-related envars - anything OMPI related is supposed to be an
 MCA param.



  On Tue, Apr 1, 2014 at 4:16 PM, Mike Dubman 
 wrote:

>  not sure what you mean, could you please provide example?
>
> comma is used often as part of the value, here is a example:
>
> -mca base_env_list "HCOLL_BCOL=basesmuma,mlnx_p2p HCOLL_SBGP=basesmuma
> ,p2p HCOLL_ML_USE_KNOMIAL_ALLREDUCE=1"
>
>
>
> On Wed, Apr 2, 2014 at 2:12 AM, Ralph Castain wrote:
>
>> This change just looks wrong - you can't split the variables on a
>> "space" as there is no way to know how many variables there might be, and
>> thus how to parse the rest of the cmd line. At best, you need a
>> comma-delimited list.
>>
>> Please fix this!
>> Ralph
>>
>>
>>
>> On Tue, Apr 1, 2014 at 2:14 PM, wrote:
>>
>>> Author: miked (Mike Dubman)
>>> Date: 2014-04-01 17:14:31 EDT (Tue, 01 Apr 2014)
>>> New Revision: 31302
>>> URL: https://svn.open-mpi.org/trac/ompi/changeset/31302
>>>
>>> Log:
>>> opal: add mca param to control ranks env variables
>>>
>>> add -mca base_env_list "var1=val1 var2=val2 ..." mca parameter that
>>> can be used in mca param files
>>> or with -am app.conf mpirun commandline to set rank env variables
>>> with mca mechanism
>>>
>>> fixed by Elena, reviewed by Miked
>>>
>>> cmr=v1.8.1:reviewer=ompi-rm1.8
>>>
>>> Text files modified:
>>>trunk/opal/mca/base/help-mca-var.txt | 5 +
>>>trunk/opal/mca/base/mca_base_var.c   |36
>>> 
>>>trunk/opal/mca/base/mca_base_var.h   | 2 ++
>>>trunk/orte/tools/orterun/orterun.c   | 2 ++
>>>4 files changed, 45 insertions(+), 0 deletions(-)
>>>
>>> Modified: trunk/opal/mca/base/help-mca-var.txt
>>>
>>> ==
>>> --- trunk/opal/mca/base/help-mca-var.txtTue Apr  1 16:57:12
>>> 2014(r31301)
>>> +++ trunk/opal/mca/base/help-mca-var.txt2014-04-01 17:14:31
>>> EDT (Tue, 01 Apr 2014)  (r31302)
>>> @@ -121,3 +121,8 @@
>>>
>>>Value:  %s
>>>Source: %s
>>> +#
>>> +[incorrect-env-list-param]
>>> +The format of mca_base_env_list parameter is incorrect. It should be
>>> +VAR1=VAL1 VAR2=VAL2 VAR3=VAL3 ...
>>> +  Value:  %s
>>>
>>> Modified: trunk/opal/mca/base/mca_base_var.c
>>>
>>> ==
>>> --- 

[hwloc-devel] Create success (hwloc git 1.9-3-g1f6ce73)

[MPI Team]

Creating nightly hwloc snapshot git tarball was a success.

Snapshot:   hwloc 1.9-3-g1f6ce73
Start time: Tue Apr  1 21:02:39 EDT 2014
End time:   Tue Apr  1 21:04:06 EDT 2014

Your friendly daemon,
Cyrador

[hwloc-devel] Create success (hwloc git dev-147-g70b9180)

[MPI Team]

Creating nightly hwloc snapshot git tarball was a success.

Snapshot:   hwloc dev-147-g70b9180
Start time: Tue Apr  1 21:01:01 EDT 2014
End time:   Tue Apr  1 21:02:30 EDT 2014

Your friendly daemon,
Cyrador

Re: [OMPI devel] [OMPI svn] svn:open-mpi r31302 - in trunk: opal/mca/base orte/tools/orterun

[Ralph Castain]

Understood - my point, however, was that we can easily add that capability
to the mca params file.. This would seem far preferable to creating a
completely new, parallel way of setting envars.

Why not do it that way?



On Tue, Apr 1, 2014 at 4:34 PM, Mike Dubman wrote:

> The "-x var=val" cannot be placed into mca params file.
>
>
> On Wed, Apr 2, 2014 at 2:34 AM, Mike Dubman wrote:
>
>> yes, it is expected that the "string" value should be quoted. will
>> clarify it in the help message and man page. Thanks for spotting.
>>
>> The underlying libraries used from OMPI
>> (mxm,psm,hcoll,glibc,pmi2,slurm,...) all have shell environment variables
>> to control their behave.
>>
>> It is unreasonable to expose mca parameter for every library tunable used
>> from ompi, but for most frequently used ones.
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Apr 2, 2014 at 2:23 AM, Ralph Castain  wrote:
>>
>>> If you are expecting the user to put quotes around the string, then you
>>> better tell them that in the help message. Otherwise, they would do what I
>>> did - simply list the envars with a space in-between, and everything fails.
>>>
>>> Also, you need to update mpirun.1in to reflect this new option or else
>>> nobody will know about it :-)
>>>
>>> However, looking at your example leaves me totally puzzled. Why are
>>> these not just MCA params to begin with, in which case we don't need
>>> another duplicate mechanism for setting them?
>>>
>>> We should only be setting envars that have nothing to do with OMPI, not
>>> setting OMPI-related envars - anything OMPI related is supposed to be an
>>> MCA param.
>>>
>>>
>>>
>>>  On Tue, Apr 1, 2014 at 4:16 PM, Mike Dubman 
>>> wrote:
>>>
  not sure what you mean, could you please provide example?

 comma is used often as part of the value, here is a example:

 -mca base_env_list "HCOLL_BCOL=basesmuma,mlnx_p2p HCOLL_SBGP=basesmuma,p2p
 HCOLL_ML_USE_KNOMIAL_ALLREDUCE=1"



 On Wed, Apr 2, 2014 at 2:12 AM, Ralph Castain  wrote:

> This change just looks wrong - you can't split the variables on a
> "space" as there is no way to know how many variables there might be, and
> thus how to parse the rest of the cmd line. At best, you need a
> comma-delimited list.
>
> Please fix this!
> Ralph
>
>
>
> On Tue, Apr 1, 2014 at 2:14 PM, wrote:
>
>> Author: miked (Mike Dubman)
>> Date: 2014-04-01 17:14:31 EDT (Tue, 01 Apr 2014)
>> New Revision: 31302
>> URL: https://svn.open-mpi.org/trac/ompi/changeset/31302
>>
>> Log:
>> opal: add mca param to control ranks env variables
>>
>> add -mca base_env_list "var1=val1 var2=val2 ..." mca parameter that
>> can be used in mca param files
>> or with -am app.conf mpirun commandline to set rank env variables
>> with mca mechanism
>>
>> fixed by Elena, reviewed by Miked
>>
>> cmr=v1.8.1:reviewer=ompi-rm1.8
>>
>> Text files modified:
>>trunk/opal/mca/base/help-mca-var.txt | 5 +
>>trunk/opal/mca/base/mca_base_var.c   |36
>> 
>>trunk/opal/mca/base/mca_base_var.h   | 2 ++
>>trunk/orte/tools/orterun/orterun.c   | 2 ++
>>4 files changed, 45 insertions(+), 0 deletions(-)
>>
>> Modified: trunk/opal/mca/base/help-mca-var.txt
>>
>> ==
>> --- trunk/opal/mca/base/help-mca-var.txtTue Apr  1 16:57:12
>> 2014(r31301)
>> +++ trunk/opal/mca/base/help-mca-var.txt2014-04-01 17:14:31
>> EDT (Tue, 01 Apr 2014)  (r31302)
>> @@ -121,3 +121,8 @@
>>
>>Value:  %s
>>Source: %s
>> +#
>> +[incorrect-env-list-param]
>> +The format of mca_base_env_list parameter is incorrect. It should be
>> +VAR1=VAL1 VAR2=VAL2 VAR3=VAL3 ...
>> +  Value:  %s
>>
>> Modified: trunk/opal/mca/base/mca_base_var.c
>>
>> ==
>> --- trunk/opal/mca/base/mca_base_var.c  Tue Apr  1 16:57:12 2014
>>(r31301)
>> +++ trunk/opal/mca/base/mca_base_var.c  2014-04-01 17:14:31 EDT (Tue,
>> 01 Apr 2014)  (r31302)
>> @@ -61,6 +61,7 @@
>>  static char *mca_base_var_override_file = NULL;
>>  static char *mca_base_var_file_prefix = NULL;
>>  static char *mca_base_param_file_path = NULL;
>> +static char *mca_base_env_list = NULL;
>>  static bool mca_base_var_suppress_override_warning = false;
>>  static opal_list_t mca_base_var_file_values;
>>  static opal_list_t mca_base_var_override_values;
>> @@ -259,6 +260,41 @@
>>  return OPAL_SUCCESS;
>>  }
>>
>> +int 

Re: [OMPI devel] [OMPI svn] svn:open-mpi r31302 - in trunk: opal/mca/base orte/tools/orterun

[Mike Dubman]

The "-x var=val" cannot be placed into mca params file.


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

> yes, it is expected that the "string" value should be quoted. will clarify
> it in the help message and man page. Thanks for spotting.
>
> The underlying libraries used from OMPI
> (mxm,psm,hcoll,glibc,pmi2,slurm,...) all have shell environment variables
> to control their behave.
>
> It is unreasonable to expose mca parameter for every library tunable used
> from ompi, but for most frequently used ones.
>
>
>
>
>
>
>
> On Wed, Apr 2, 2014 at 2:23 AM, Ralph Castain  wrote:
>
>> If you are expecting the user to put quotes around the string, then you
>> better tell them that in the help message. Otherwise, they would do what I
>> did - simply list the envars with a space in-between, and everything fails.
>>
>> Also, you need to update mpirun.1in to reflect this new option or else
>> nobody will know about it :-)
>>
>> However, looking at your example leaves me totally puzzled. Why are these
>> not just MCA params to begin with, in which case we don't need another
>> duplicate mechanism for setting them?
>>
>> We should only be setting envars that have nothing to do with OMPI, not
>> setting OMPI-related envars - anything OMPI related is supposed to be an
>> MCA param.
>>
>>
>>
>>  On Tue, Apr 1, 2014 at 4:16 PM, Mike Dubman wrote:
>>
>>>  not sure what you mean, could you please provide example?
>>>
>>> comma is used often as part of the value, here is a example:
>>>
>>> -mca base_env_list "HCOLL_BCOL=basesmuma,mlnx_p2p HCOLL_SBGP=basesmuma,p2p
>>> HCOLL_ML_USE_KNOMIAL_ALLREDUCE=1"
>>>
>>>
>>>
>>> On Wed, Apr 2, 2014 at 2:12 AM, Ralph Castain  wrote:
>>>
 This change just looks wrong - you can't split the variables on a
 "space" as there is no way to know how many variables there might be, and
 thus how to parse the rest of the cmd line. At best, you need a
 comma-delimited list.

 Please fix this!
 Ralph



 On Tue, Apr 1, 2014 at 2:14 PM,  wrote:

> Author: miked (Mike Dubman)
> Date: 2014-04-01 17:14:31 EDT (Tue, 01 Apr 2014)
> New Revision: 31302
> URL: https://svn.open-mpi.org/trac/ompi/changeset/31302
>
> Log:
> opal: add mca param to control ranks env variables
>
> add -mca base_env_list "var1=val1 var2=val2 ..." mca parameter that
> can be used in mca param files
> or with -am app.conf mpirun commandline to set rank env variables with
> mca mechanism
>
> fixed by Elena, reviewed by Miked
>
> cmr=v1.8.1:reviewer=ompi-rm1.8
>
> Text files modified:
>trunk/opal/mca/base/help-mca-var.txt | 5 +
>trunk/opal/mca/base/mca_base_var.c   |36
> 
>trunk/opal/mca/base/mca_base_var.h   | 2 ++
>trunk/orte/tools/orterun/orterun.c   | 2 ++
>4 files changed, 45 insertions(+), 0 deletions(-)
>
> Modified: trunk/opal/mca/base/help-mca-var.txt
>
> ==
> --- trunk/opal/mca/base/help-mca-var.txtTue Apr  1 16:57:12
> 2014(r31301)
> +++ trunk/opal/mca/base/help-mca-var.txt2014-04-01 17:14:31
> EDT (Tue, 01 Apr 2014)  (r31302)
> @@ -121,3 +121,8 @@
>
>Value:  %s
>Source: %s
> +#
> +[incorrect-env-list-param]
> +The format of mca_base_env_list parameter is incorrect. It should be
> +VAR1=VAL1 VAR2=VAL2 VAR3=VAL3 ...
> +  Value:  %s
>
> Modified: trunk/opal/mca/base/mca_base_var.c
>
> ==
> --- trunk/opal/mca/base/mca_base_var.c  Tue Apr  1 16:57:12 2014
>  (r31301)
> +++ trunk/opal/mca/base/mca_base_var.c  2014-04-01 17:14:31 EDT (Tue,
> 01 Apr 2014)  (r31302)
> @@ -61,6 +61,7 @@
>  static char *mca_base_var_override_file = NULL;
>  static char *mca_base_var_file_prefix = NULL;
>  static char *mca_base_param_file_path = NULL;
> +static char *mca_base_env_list = NULL;
>  static bool mca_base_var_suppress_override_warning = false;
>  static opal_list_t mca_base_var_file_values;
>  static opal_list_t mca_base_var_override_values;
> @@ -259,6 +260,41 @@
>  return OPAL_SUCCESS;
>  }
>
> +int mca_base_var_process_env_list(char ***context_env)
> +{
> +int i, ret;
> +char** tokens;
> +char* ptr;
> +char* param, *value;
> +ret = mca_base_var_register ("opal", "mca", "base", "env_list",
> + "Set SHELL env variables",
> + MCA_BASE_VAR_TYPE_STRING, NULL, 0,
> 0, OPAL_INFO_LVL_3,
> + 

Re: [OMPI devel] [OMPI svn] svn:open-mpi r31302 - in trunk: opal/mca/base orte/tools/orterun

[Mike Dubman]

yes, it is expected that the "string" value should be quoted. will clarify
it in the help message and man page. Thanks for spotting.

The underlying libraries used from OMPI
(mxm,psm,hcoll,glibc,pmi2,slurm,...) all have shell environment variables
to control their behave.

It is unreasonable to expose mca parameter for every library tunable used
from ompi, but for most frequently used ones.







On Wed, Apr 2, 2014 at 2:23 AM, Ralph Castain  wrote:

> If you are expecting the user to put quotes around the string, then you
> better tell them that in the help message. Otherwise, they would do what I
> did - simply list the envars with a space in-between, and everything fails.
>
> Also, you need to update mpirun.1in to reflect this new option or else
> nobody will know about it :-)
>
> However, looking at your example leaves me totally puzzled. Why are these
> not just MCA params to begin with, in which case we don't need another
> duplicate mechanism for setting them?
>
> We should only be setting envars that have nothing to do with OMPI, not
> setting OMPI-related envars - anything OMPI related is supposed to be an
> MCA param.
>
>
>
> On Tue, Apr 1, 2014 at 4:16 PM, Mike Dubman wrote:
>
>> not sure what you mean, could you please provide example?
>>
>> comma is used often as part of the value, here is a example:
>>
>> -mca base_env_list "HCOLL_BCOL=basesmuma,mlnx_p2p HCOLL_SBGP=basesmuma,p2p
>> HCOLL_ML_USE_KNOMIAL_ALLREDUCE=1"
>>
>>
>>
>> On Wed, Apr 2, 2014 at 2:12 AM, Ralph Castain  wrote:
>>
>>> This change just looks wrong - you can't split the variables on a
>>> "space" as there is no way to know how many variables there might be, and
>>> thus how to parse the rest of the cmd line. At best, you need a
>>> comma-delimited list.
>>>
>>> Please fix this!
>>> Ralph
>>>
>>>
>>>
>>> On Tue, Apr 1, 2014 at 2:14 PM,  wrote:
>>>
 Author: miked (Mike Dubman)
 Date: 2014-04-01 17:14:31 EDT (Tue, 01 Apr 2014)
 New Revision: 31302
 URL: https://svn.open-mpi.org/trac/ompi/changeset/31302

 Log:
 opal: add mca param to control ranks env variables

 add -mca base_env_list "var1=val1 var2=val2 ..." mca parameter that can
 be used in mca param files
 or with -am app.conf mpirun commandline to set rank env variables with
 mca mechanism

 fixed by Elena, reviewed by Miked

 cmr=v1.8.1:reviewer=ompi-rm1.8

 Text files modified:
trunk/opal/mca/base/help-mca-var.txt | 5 +
trunk/opal/mca/base/mca_base_var.c   |36
 
trunk/opal/mca/base/mca_base_var.h   | 2 ++
trunk/orte/tools/orterun/orterun.c   | 2 ++
4 files changed, 45 insertions(+), 0 deletions(-)

 Modified: trunk/opal/mca/base/help-mca-var.txt

 ==
 --- trunk/opal/mca/base/help-mca-var.txtTue Apr  1 16:57:12
 2014(r31301)
 +++ trunk/opal/mca/base/help-mca-var.txt2014-04-01 17:14:31 EDT
 (Tue, 01 Apr 2014)  (r31302)
 @@ -121,3 +121,8 @@

Value:  %s
Source: %s
 +#
 +[incorrect-env-list-param]
 +The format of mca_base_env_list parameter is incorrect. It should be
 +VAR1=VAL1 VAR2=VAL2 VAR3=VAL3 ...
 +  Value:  %s

 Modified: trunk/opal/mca/base/mca_base_var.c

 ==
 --- trunk/opal/mca/base/mca_base_var.c  Tue Apr  1 16:57:12 2014
  (r31301)
 +++ trunk/opal/mca/base/mca_base_var.c  2014-04-01 17:14:31 EDT (Tue,
 01 Apr 2014)  (r31302)
 @@ -61,6 +61,7 @@
  static char *mca_base_var_override_file = NULL;
  static char *mca_base_var_file_prefix = NULL;
  static char *mca_base_param_file_path = NULL;
 +static char *mca_base_env_list = NULL;
  static bool mca_base_var_suppress_override_warning = false;
  static opal_list_t mca_base_var_file_values;
  static opal_list_t mca_base_var_override_values;
 @@ -259,6 +260,41 @@
  return OPAL_SUCCESS;
  }

 +int mca_base_var_process_env_list(char ***context_env)
 +{
 +int i, ret;
 +char** tokens;
 +char* ptr;
 +char* param, *value;
 +ret = mca_base_var_register ("opal", "mca", "base", "env_list",
 + "Set SHELL env variables",
 + MCA_BASE_VAR_TYPE_STRING, NULL, 0, 0,
 OPAL_INFO_LVL_3,
 + MCA_BASE_VAR_SCOPE_READONLY,
 _base_env_list);
 +if ((0 > ret) || (NULL == mca_base_env_list)) {
 +return ret;
 +}
 +tokens = opal_argv_split(mca_base_env_list, ' ');
 +if (NULL != tokens) {
 +for (i = 0; NULL != tokens[i]; 

Re: [OMPI devel] [OMPI svn] svn:open-mpi r31302 - in trunk: opal/mca/base orte/tools/orterun

[Ralph Castain]

Actually, the more I think about this, the more puzzled I get. We already
have a mechanism for forwarding and/or setting envars, though it applies to
the daemons, who then drop it down to the apps. Just use the "-x" option,
which will either forward the current value of the envar, or you can set
the value explicitly with "-x foo=var".

So what does this new capability add? Is it just the ability to do -x from
within an am-file? If so, why not just update the am parser to support it?

If -x isn't working, or isn't doing something we want, then it might be
better to update it as opposed to creating another parallel mechanism...



On Tue, Apr 1, 2014 at 4:23 PM, Ralph Castain  wrote:

> If you are expecting the user to put quotes around the string, then you
> better tell them that in the help message. Otherwise, they would do what I
> did - simply list the envars with a space in-between, and everything fails.
>
> Also, you need to update mpirun.1in to reflect this new option or else
> nobody will know about it :-)
>
> However, looking at your example leaves me totally puzzled. Why are these
> not just MCA params to begin with, in which case we don't need another
> duplicate mechanism for setting them?
>
> We should only be setting envars that have nothing to do with OMPI, not
> setting OMPI-related envars - anything OMPI related is supposed to be an
> MCA param.
>
>
>
> On Tue, Apr 1, 2014 at 4:16 PM, Mike Dubman wrote:
>
>> not sure what you mean, could you please provide example?
>>
>> comma is used often as part of the value, here is a example:
>>
>> -mca base_env_list "HCOLL_BCOL=basesmuma,mlnx_p2p HCOLL_SBGP=basesmuma,p2p
>> HCOLL_ML_USE_KNOMIAL_ALLREDUCE=1"
>>
>>
>>
>> On Wed, Apr 2, 2014 at 2:12 AM, Ralph Castain  wrote:
>>
>>> This change just looks wrong - you can't split the variables on a
>>> "space" as there is no way to know how many variables there might be, and
>>> thus how to parse the rest of the cmd line. At best, you need a
>>> comma-delimited list.
>>>
>>> Please fix this!
>>> Ralph
>>>
>>>
>>>
>>> On Tue, Apr 1, 2014 at 2:14 PM,  wrote:
>>>
 Author: miked (Mike Dubman)
 Date: 2014-04-01 17:14:31 EDT (Tue, 01 Apr 2014)
 New Revision: 31302
 URL: https://svn.open-mpi.org/trac/ompi/changeset/31302

 Log:
 opal: add mca param to control ranks env variables

 add -mca base_env_list "var1=val1 var2=val2 ..." mca parameter that can
 be used in mca param files
 or with -am app.conf mpirun commandline to set rank env variables with
 mca mechanism

 fixed by Elena, reviewed by Miked

 cmr=v1.8.1:reviewer=ompi-rm1.8

 Text files modified:
trunk/opal/mca/base/help-mca-var.txt | 5 +
trunk/opal/mca/base/mca_base_var.c   |36
 
trunk/opal/mca/base/mca_base_var.h   | 2 ++
trunk/orte/tools/orterun/orterun.c   | 2 ++
4 files changed, 45 insertions(+), 0 deletions(-)

 Modified: trunk/opal/mca/base/help-mca-var.txt

 ==
 --- trunk/opal/mca/base/help-mca-var.txtTue Apr  1 16:57:12
 2014(r31301)
 +++ trunk/opal/mca/base/help-mca-var.txt2014-04-01 17:14:31 EDT
 (Tue, 01 Apr 2014)  (r31302)
 @@ -121,3 +121,8 @@

Value:  %s
Source: %s
 +#
 +[incorrect-env-list-param]
 +The format of mca_base_env_list parameter is incorrect. It should be
 +VAR1=VAL1 VAR2=VAL2 VAR3=VAL3 ...
 +  Value:  %s

 Modified: trunk/opal/mca/base/mca_base_var.c

 ==
 --- trunk/opal/mca/base/mca_base_var.c  Tue Apr  1 16:57:12 2014
  (r31301)
 +++ trunk/opal/mca/base/mca_base_var.c  2014-04-01 17:14:31 EDT (Tue,
 01 Apr 2014)  (r31302)
 @@ -61,6 +61,7 @@
  static char *mca_base_var_override_file = NULL;
  static char *mca_base_var_file_prefix = NULL;
  static char *mca_base_param_file_path = NULL;
 +static char *mca_base_env_list = NULL;
  static bool mca_base_var_suppress_override_warning = false;
  static opal_list_t mca_base_var_file_values;
  static opal_list_t mca_base_var_override_values;
 @@ -259,6 +260,41 @@
  return OPAL_SUCCESS;
  }

 +int mca_base_var_process_env_list(char ***context_env)
 +{
 +int i, ret;
 +char** tokens;
 +char* ptr;
 +char* param, *value;
 +ret = mca_base_var_register ("opal", "mca", "base", "env_list",
 + "Set SHELL env variables",
 + MCA_BASE_VAR_TYPE_STRING, NULL, 0, 0,
 OPAL_INFO_LVL_3,
 + MCA_BASE_VAR_SCOPE_READONLY,
 

Re: [OMPI devel] [OMPI svn] svn:open-mpi r31302 - in trunk: opal/mca/base orte/tools/orterun

[Ralph Castain]

If you are expecting the user to put quotes around the string, then you
better tell them that in the help message. Otherwise, they would do what I
did - simply list the envars with a space in-between, and everything fails.

Also, you need to update mpirun.1in to reflect this new option or else
nobody will know about it :-)

However, looking at your example leaves me totally puzzled. Why are these
not just MCA params to begin with, in which case we don't need another
duplicate mechanism for setting them?

We should only be setting envars that have nothing to do with OMPI, not
setting OMPI-related envars - anything OMPI related is supposed to be an
MCA param.



On Tue, Apr 1, 2014 at 4:16 PM, Mike Dubman wrote:

> not sure what you mean, could you please provide example?
>
> comma is used often as part of the value, here is a example:
>
> -mca base_env_list "HCOLL_BCOL=basesmuma,mlnx_p2p HCOLL_SBGP=basesmuma,p2p
> HCOLL_ML_USE_KNOMIAL_ALLREDUCE=1"
>
>
>
> On Wed, Apr 2, 2014 at 2:12 AM, Ralph Castain  wrote:
>
>> This change just looks wrong - you can't split the variables on a "space"
>> as there is no way to know how many variables there might be, and thus how
>> to parse the rest of the cmd line. At best, you need a comma-delimited list.
>>
>> Please fix this!
>> Ralph
>>
>>
>>
>> On Tue, Apr 1, 2014 at 2:14 PM,  wrote:
>>
>>> Author: miked (Mike Dubman)
>>> Date: 2014-04-01 17:14:31 EDT (Tue, 01 Apr 2014)
>>> New Revision: 31302
>>> URL: https://svn.open-mpi.org/trac/ompi/changeset/31302
>>>
>>> Log:
>>> opal: add mca param to control ranks env variables
>>>
>>> add -mca base_env_list "var1=val1 var2=val2 ..." mca parameter that can
>>> be used in mca param files
>>> or with -am app.conf mpirun commandline to set rank env variables with
>>> mca mechanism
>>>
>>> fixed by Elena, reviewed by Miked
>>>
>>> cmr=v1.8.1:reviewer=ompi-rm1.8
>>>
>>> Text files modified:
>>>trunk/opal/mca/base/help-mca-var.txt | 5 +
>>>trunk/opal/mca/base/mca_base_var.c   |36
>>> 
>>>trunk/opal/mca/base/mca_base_var.h   | 2 ++
>>>trunk/orte/tools/orterun/orterun.c   | 2 ++
>>>4 files changed, 45 insertions(+), 0 deletions(-)
>>>
>>> Modified: trunk/opal/mca/base/help-mca-var.txt
>>>
>>> ==
>>> --- trunk/opal/mca/base/help-mca-var.txtTue Apr  1 16:57:12 2014
>>>(r31301)
>>> +++ trunk/opal/mca/base/help-mca-var.txt2014-04-01 17:14:31 EDT
>>> (Tue, 01 Apr 2014)  (r31302)
>>> @@ -121,3 +121,8 @@
>>>
>>>Value:  %s
>>>Source: %s
>>> +#
>>> +[incorrect-env-list-param]
>>> +The format of mca_base_env_list parameter is incorrect. It should be
>>> +VAR1=VAL1 VAR2=VAL2 VAR3=VAL3 ...
>>> +  Value:  %s
>>>
>>> Modified: trunk/opal/mca/base/mca_base_var.c
>>>
>>> ==
>>> --- trunk/opal/mca/base/mca_base_var.c  Tue Apr  1 16:57:12 2014
>>>  (r31301)
>>> +++ trunk/opal/mca/base/mca_base_var.c  2014-04-01 17:14:31 EDT (Tue, 01
>>> Apr 2014)  (r31302)
>>> @@ -61,6 +61,7 @@
>>>  static char *mca_base_var_override_file = NULL;
>>>  static char *mca_base_var_file_prefix = NULL;
>>>  static char *mca_base_param_file_path = NULL;
>>> +static char *mca_base_env_list = NULL;
>>>  static bool mca_base_var_suppress_override_warning = false;
>>>  static opal_list_t mca_base_var_file_values;
>>>  static opal_list_t mca_base_var_override_values;
>>> @@ -259,6 +260,41 @@
>>>  return OPAL_SUCCESS;
>>>  }
>>>
>>> +int mca_base_var_process_env_list(char ***context_env)
>>> +{
>>> +int i, ret;
>>> +char** tokens;
>>> +char* ptr;
>>> +char* param, *value;
>>> +ret = mca_base_var_register ("opal", "mca", "base", "env_list",
>>> + "Set SHELL env variables",
>>> + MCA_BASE_VAR_TYPE_STRING, NULL, 0, 0,
>>> OPAL_INFO_LVL_3,
>>> + MCA_BASE_VAR_SCOPE_READONLY,
>>> _base_env_list);
>>> +if ((0 > ret) || (NULL == mca_base_env_list)) {
>>> +return ret;
>>> +}
>>> +tokens = opal_argv_split(mca_base_env_list, ' ');
>>> +if (NULL != tokens) {
>>> +for (i = 0; NULL != tokens[i]; i++) {
>>> +if (NULL == (ptr = strchr(tokens[i], '='))) {
>>> +opal_show_help("help-mca-var.txt",
>>> "incorrect-env-list-param",
>>> +true, mca_base_env_list);
>>> +opal_argv_free(tokens);
>>> +return OPAL_ERROR;
>>> +} else {
>>> +param = strdup(tokens[i]);
>>> +value = strchr(param, '=');
>>> +*value = '\0';
>>> +value++;
>>> +opal_setenv(param, value, false, context_env);
>>> +free(param);
>>> +}
>>> 

Re: [OMPI devel] openmpi-1.8 - hangup using more than 4 nodes under managed state by Torque

[tmishima]

Thanks Ralph.

Tetsuya

> I tracked it down - not Torque specific, but impacts all managed
environments. Will fix
>
>
> On Apr 1, 2014, at 2:23 AM, tmish...@jcity.maeda.co.jp wrote:
>
> >
> > Hi Ralph,
> >
> > I saw another hangup with openmpi-1.8 when I used more than 4 nodes
> > (having 8 cores each) under managed state by Torque. Although I'm not
> > sure you can reproduce it with SLURM, at leaset with Torque it can be
> > reproduced in this way:
> >
> > [mishima@manage ~]$ qsub -I -l nodes=4:ppn=8
> > qsub: waiting for job 8726.manage.cluster to start
> > qsub: job 8726.manage.cluster ready
> >
> > [mishima@node09 ~]$ mpirun -np 65 ~/mis/openmpi/demos/myprog
> >
--
> > There are not enough slots available in the system to satisfy the 65
slots
> > that were requested by the application:
> >  /home/mishima/mis/openmpi/demos/myprog
> >
> > Either request fewer slots for your application, or make more slots
> > available
> > for use.
> >
--
> > <<< HANG HERE!! >>>
> > Abort is in progress...hit ctrl-c again within 5 seconds to forcibly
> > terminate
> >
> > I found this behavior when I happened to input wrong procs. With less
than
> > 4
> > nodes or rsh - namely unmanaged state, it works. I'm afraid to say I
have
> > no
> > idea how to resolve it. I hope you could fix the problem.
> >
> > Tetsuya
> >
> > ___
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Searchable archives:
http://www.open-mpi.org/community/lists/devel/2014/04/index.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/14438.php

Re: [OMPI devel] [OMPI svn] svn:open-mpi r31302 - in trunk: opal/mca/base orte/tools/orterun

[Mike Dubman]

not sure what you mean, could you please provide example?

comma is used often as part of the value, here is a example:

-mca base_env_list "HCOLL_BCOL=basesmuma,mlnx_p2p HCOLL_SBGP=basesmuma,p2p
HCOLL_ML_USE_KNOMIAL_ALLREDUCE=1"



On Wed, Apr 2, 2014 at 2:12 AM, Ralph Castain  wrote:

> This change just looks wrong - you can't split the variables on a "space"
> as there is no way to know how many variables there might be, and thus how
> to parse the rest of the cmd line. At best, you need a comma-delimited list.
>
> Please fix this!
> Ralph
>
>
>
> On Tue, Apr 1, 2014 at 2:14 PM,  wrote:
>
>> Author: miked (Mike Dubman)
>> Date: 2014-04-01 17:14:31 EDT (Tue, 01 Apr 2014)
>> New Revision: 31302
>> URL: https://svn.open-mpi.org/trac/ompi/changeset/31302
>>
>> Log:
>> opal: add mca param to control ranks env variables
>>
>> add -mca base_env_list "var1=val1 var2=val2 ..." mca parameter that can
>> be used in mca param files
>> or with -am app.conf mpirun commandline to set rank env variables with
>> mca mechanism
>>
>> fixed by Elena, reviewed by Miked
>>
>> cmr=v1.8.1:reviewer=ompi-rm1.8
>>
>> Text files modified:
>>trunk/opal/mca/base/help-mca-var.txt | 5 +
>>trunk/opal/mca/base/mca_base_var.c   |36
>> 
>>trunk/opal/mca/base/mca_base_var.h   | 2 ++
>>trunk/orte/tools/orterun/orterun.c   | 2 ++
>>4 files changed, 45 insertions(+), 0 deletions(-)
>>
>> Modified: trunk/opal/mca/base/help-mca-var.txt
>>
>> ==
>> --- trunk/opal/mca/base/help-mca-var.txtTue Apr  1 16:57:12 2014
>>(r31301)
>> +++ trunk/opal/mca/base/help-mca-var.txt2014-04-01 17:14:31 EDT
>> (Tue, 01 Apr 2014)  (r31302)
>> @@ -121,3 +121,8 @@
>>
>>Value:  %s
>>Source: %s
>> +#
>> +[incorrect-env-list-param]
>> +The format of mca_base_env_list parameter is incorrect. It should be
>> +VAR1=VAL1 VAR2=VAL2 VAR3=VAL3 ...
>> +  Value:  %s
>>
>> Modified: trunk/opal/mca/base/mca_base_var.c
>>
>> ==
>> --- trunk/opal/mca/base/mca_base_var.c  Tue Apr  1 16:57:12 2014
>>  (r31301)
>> +++ trunk/opal/mca/base/mca_base_var.c  2014-04-01 17:14:31 EDT (Tue, 01
>> Apr 2014)  (r31302)
>> @@ -61,6 +61,7 @@
>>  static char *mca_base_var_override_file = NULL;
>>  static char *mca_base_var_file_prefix = NULL;
>>  static char *mca_base_param_file_path = NULL;
>> +static char *mca_base_env_list = NULL;
>>  static bool mca_base_var_suppress_override_warning = false;
>>  static opal_list_t mca_base_var_file_values;
>>  static opal_list_t mca_base_var_override_values;
>> @@ -259,6 +260,41 @@
>>  return OPAL_SUCCESS;
>>  }
>>
>> +int mca_base_var_process_env_list(char ***context_env)
>> +{
>> +int i, ret;
>> +char** tokens;
>> +char* ptr;
>> +char* param, *value;
>> +ret = mca_base_var_register ("opal", "mca", "base", "env_list",
>> + "Set SHELL env variables",
>> + MCA_BASE_VAR_TYPE_STRING, NULL, 0, 0,
>> OPAL_INFO_LVL_3,
>> + MCA_BASE_VAR_SCOPE_READONLY,
>> _base_env_list);
>> +if ((0 > ret) || (NULL == mca_base_env_list)) {
>> +return ret;
>> +}
>> +tokens = opal_argv_split(mca_base_env_list, ' ');
>> +if (NULL != tokens) {
>> +for (i = 0; NULL != tokens[i]; i++) {
>> +if (NULL == (ptr = strchr(tokens[i], '='))) {
>> +opal_show_help("help-mca-var.txt",
>> "incorrect-env-list-param",
>> +true, mca_base_env_list);
>> +opal_argv_free(tokens);
>> +return OPAL_ERROR;
>> +} else {
>> +param = strdup(tokens[i]);
>> +value = strchr(param, '=');
>> +*value = '\0';
>> +value++;
>> +opal_setenv(param, value, false, context_env);
>> +free(param);
>> +}
>> +}
>> +opal_argv_free(tokens);
>> +}
>> +return OPAL_SUCCESS;
>> +}
>> +
>>  static int mca_base_var_cache_files(bool rel_path_search)
>>  {
>>  char *tmp;
>>
>> Modified: trunk/opal/mca/base/mca_base_var.h
>>
>> ==
>> --- trunk/opal/mca/base/mca_base_var.h  Tue Apr  1 16:57:12 2014
>>  (r31301)
>> +++ trunk/opal/mca/base/mca_base_var.h  2014-04-01 17:14:31 EDT (Tue, 01
>> Apr 2014)  (r31302)
>> @@ -716,6 +716,8 @@
>>   */
>>  OPAL_DECLSPEC int mca_base_var_dump(int vari, char ***out,
>> mca_base_var_dump_type_t output_type);
>>
>> +OPAL_DECLSPEC int mca_base_var_process_env_list(char ***context_env);
>> +
>>  END_C_DECLS
>>
>>  #endif /* OPAL_MCA_BASE_VAR_H */
>>
>> Modified: trunk/orte/tools/orterun/orterun.c
>>
>> 

Re: [OMPI devel] [OMPI svn] svn:open-mpi r31302 - in trunk: opal/mca/base orte/tools/orterun

[Ralph Castain]

This change just looks wrong - you can't split the variables on a "space"
as there is no way to know how many variables there might be, and thus how
to parse the rest of the cmd line. At best, you need a comma-delimited list.

Please fix this!
Ralph



On Tue, Apr 1, 2014 at 2:14 PM,  wrote:

> Author: miked (Mike Dubman)
> Date: 2014-04-01 17:14:31 EDT (Tue, 01 Apr 2014)
> New Revision: 31302
> URL: https://svn.open-mpi.org/trac/ompi/changeset/31302
>
> Log:
> opal: add mca param to control ranks env variables
>
> add -mca base_env_list "var1=val1 var2=val2 ..." mca parameter that can be
> used in mca param files
> or with -am app.conf mpirun commandline to set rank env variables with mca
> mechanism
>
> fixed by Elena, reviewed by Miked
>
> cmr=v1.8.1:reviewer=ompi-rm1.8
>
> Text files modified:
>trunk/opal/mca/base/help-mca-var.txt | 5 +
>trunk/opal/mca/base/mca_base_var.c   |36
> 
>trunk/opal/mca/base/mca_base_var.h   | 2 ++
>trunk/orte/tools/orterun/orterun.c   | 2 ++
>4 files changed, 45 insertions(+), 0 deletions(-)
>
> Modified: trunk/opal/mca/base/help-mca-var.txt
>
> ==
> --- trunk/opal/mca/base/help-mca-var.txtTue Apr  1 16:57:12 2014
>  (r31301)
> +++ trunk/opal/mca/base/help-mca-var.txt2014-04-01 17:14:31 EDT
> (Tue, 01 Apr 2014)  (r31302)
> @@ -121,3 +121,8 @@
>
>Value:  %s
>Source: %s
> +#
> +[incorrect-env-list-param]
> +The format of mca_base_env_list parameter is incorrect. It should be
> +VAR1=VAL1 VAR2=VAL2 VAR3=VAL3 ...
> +  Value:  %s
>
> Modified: trunk/opal/mca/base/mca_base_var.c
>
> ==
> --- trunk/opal/mca/base/mca_base_var.c  Tue Apr  1 16:57:12 2014
>  (r31301)
> +++ trunk/opal/mca/base/mca_base_var.c  2014-04-01 17:14:31 EDT (Tue, 01
> Apr 2014)  (r31302)
> @@ -61,6 +61,7 @@
>  static char *mca_base_var_override_file = NULL;
>  static char *mca_base_var_file_prefix = NULL;
>  static char *mca_base_param_file_path = NULL;
> +static char *mca_base_env_list = NULL;
>  static bool mca_base_var_suppress_override_warning = false;
>  static opal_list_t mca_base_var_file_values;
>  static opal_list_t mca_base_var_override_values;
> @@ -259,6 +260,41 @@
>  return OPAL_SUCCESS;
>  }
>
> +int mca_base_var_process_env_list(char ***context_env)
> +{
> +int i, ret;
> +char** tokens;
> +char* ptr;
> +char* param, *value;
> +ret = mca_base_var_register ("opal", "mca", "base", "env_list",
> + "Set SHELL env variables",
> + MCA_BASE_VAR_TYPE_STRING, NULL, 0, 0,
> OPAL_INFO_LVL_3,
> + MCA_BASE_VAR_SCOPE_READONLY,
> _base_env_list);
> +if ((0 > ret) || (NULL == mca_base_env_list)) {
> +return ret;
> +}
> +tokens = opal_argv_split(mca_base_env_list, ' ');
> +if (NULL != tokens) {
> +for (i = 0; NULL != tokens[i]; i++) {
> +if (NULL == (ptr = strchr(tokens[i], '='))) {
> +opal_show_help("help-mca-var.txt",
> "incorrect-env-list-param",
> +true, mca_base_env_list);
> +opal_argv_free(tokens);
> +return OPAL_ERROR;
> +} else {
> +param = strdup(tokens[i]);
> +value = strchr(param, '=');
> +*value = '\0';
> +value++;
> +opal_setenv(param, value, false, context_env);
> +free(param);
> +}
> +}
> +opal_argv_free(tokens);
> +}
> +return OPAL_SUCCESS;
> +}
> +
>  static int mca_base_var_cache_files(bool rel_path_search)
>  {
>  char *tmp;
>
> Modified: trunk/opal/mca/base/mca_base_var.h
>
> ==
> --- trunk/opal/mca/base/mca_base_var.h  Tue Apr  1 16:57:12 2014
>  (r31301)
> +++ trunk/opal/mca/base/mca_base_var.h  2014-04-01 17:14:31 EDT (Tue, 01
> Apr 2014)  (r31302)
> @@ -716,6 +716,8 @@
>   */
>  OPAL_DECLSPEC int mca_base_var_dump(int vari, char ***out,
> mca_base_var_dump_type_t output_type);
>
> +OPAL_DECLSPEC int mca_base_var_process_env_list(char ***context_env);
> +
>  END_C_DECLS
>
>  #endif /* OPAL_MCA_BASE_VAR_H */
>
> Modified: trunk/orte/tools/orterun/orterun.c
>
> ==
> --- trunk/orte/tools/orterun/orterun.c  Tue Apr  1 16:57:12 2014
>  (r31301)
> +++ trunk/orte/tools/orterun/orterun.c  2014-04-01 17:14:31 EDT (Tue, 01
> Apr 2014)  (r31302)
> @@ -1628,6 +1628,8 @@
>  goto cleanup;
>  }
>  mca_base_cmd_line_process_args(_line, app_env, _mca_env);
> +mca_base_var_process_env_list(app_env);
> +
>
>  /* Is there an appfile in here? */
>
> 

[OMPI devel] Problem of running 'mpirun' on a cross-compiled openmpi-1.6.5 for armv7

[Allan Wu]

Hello everyone,

I am trying to run OpenMPI-1.6.5 on a Linux on a system based on ARM Cortex
A9. The linux system and the hardware is provided by Xilinx Inc., and for
those who may have related experiences the system is called Zynq, which is
an embedded SoC system with ARM cores and FPGA fabrics. Xilinx has provided
cross-compiler for the system, which I used to compile openmpi, and the
compilation is successful. Here is the configuration script I used for the

compilation:
./configure --build=arm-linux-gnueabi --host=armv7-linux-gnueabi  \
--disable-mpi-f77 --disable-mpi-f90 \
--disable-mpi-cxx --prefix=`pwd`/install \
--with-devel-headers --enable-binaries \
--enable-shared --enable-static \
--disable-mmap-shmem --disable-posix-shmem --disable-sysv-shmem \
--disable-dlopen

For the cross-compiler, I have set the environmental variables "CC" and
"CXX".

When I launch 'mpirun' on the ARM linux, I got the error like this:

It looks like opal_init failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems.  This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):

  opal_shmem_base_select failed
  --> Returned value -1 instead of OPAL_SUCCESS
--
[ZC702:01353] [[INVALID],INVALID] ORTE_ERROR_LOG: Error in file
runtime/orte_init.c at line 79
[ZC702:01353] [[INVALID],INVALID] ORTE_ERROR_LOG: Error in file orterun.c
at line 694

I have compressed the information from 'ompi-info --all' in the attachment.

For some more related information, I have been tuning the configuration
settings for a while, and I am afraid some of them may not be quite
appropriate. My general goal is to enable message passing in my system of
several such chips connected via Ethernet. So I will not launch more than
one process on any single machine. That's why I wanted to disable the
shared memory support. Although that doesn't change the outcome for me.
I also got a lot of error messages on mca failing to find components, that
is why I tried disable dlopen.

I am also looking for suggestions. Basically I want to compile a "clean"
version of OpenMPI with only the core message passing support, that may
automatically get rid of a lot of the headache of the cross-compilation.
When I searched through the documentation, I came to notice the idea of
Portable Hardware locality (hwloc), however, the idea is completely new to
me so I do not know if that would be relevant for my case.

Thank you in advance for your suggestions! Please tell me if I need to
provide further information of my system.

Regards,
--
Di Wu (Allan)
VAST Labortory (http://vast.cs.ucla.edu/),
Department of Computer Science, UC Los Angeles
Email: al...@cs.ucla.edu


log.tar.gz
Description: GNU Zip compressed data

[OMPI devel] Seeking input for an RFC

[Joshua Ladd]

Soliciting input from the community:


WHAT:  Modify PML cm component to remove unnecessary initializations, 
optimizing blocking operations

WHY:Remove overhead in fast-path by allowing a "direct mode" increases 
single packet latency

HOW:In PML cm, even if the request starts and ends within the scope of the 
blocking send/recv function,
  A full request, a structure of up to 488 bytes (not including the 
MTL request appendix size) may be initialized.
  The request includes the opmi_request_t structure, used by an 
underlying MTL component, the converter
  which corresponds to the datatype and other parameters - some of 
which are stored and only used if the
  request is asynchronous. This causes a significant amount of 
writes, especially when considering the send
  buffer could be as small as several bytes.

  The proposed patch introduces a "direct mode" (currently set iff 
the underlying MTL is "mxm", which is the
  only option I had available for testing), which when on cuts most 
of the initialization for blocking send and
  receive operations to include only the bare minimum required to 
function. Aside from initializing only a part
  of the request structure (field like "dst" and "tag" are passed 
again to the MTL_CALL macro rather than use
  the request struct anyway), the function uses a single 
pre-allocated request buffer - which is possible since
  the call is blocking. Our tests show that this increases packet 
rate by approximately 20% with 8-byte buffers.
  Note that the "redundant" if-conditions for irrelevant functions 
(e.g. recv_init) are removed by compiler,
  since the macro substitutes and gets "if (0 == 0)".

WHERE: Most of the files in ompi/mca/pml/cm .

WHEN:   ?



Joshua S. Ladd, PhD
HPC Algorithms Engineer
Mellanox Technologies

Email: josh...@mellanox.com
Cell: +1 (865) 258 - 8898

Re: [OMPI devel] openmpi-1.8 - hangup using more than 4 nodes under managed state by Torque

[Ralph Castain]

I tracked it down - not Torque specific, but impacts all managed environments. 
Will fix


On Apr 1, 2014, at 2:23 AM, tmish...@jcity.maeda.co.jp wrote:

> 
> Hi Ralph,
> 
> I saw another hangup with openmpi-1.8 when I used more than 4 nodes
> (having 8 cores each) under managed state by Torque. Although I'm not
> sure you can reproduce it with SLURM, at leaset with Torque it can be
> reproduced in this way:
> 
> [mishima@manage ~]$ qsub -I -l nodes=4:ppn=8
> qsub: waiting for job 8726.manage.cluster to start
> qsub: job 8726.manage.cluster ready
> 
> [mishima@node09 ~]$ mpirun -np 65 ~/mis/openmpi/demos/myprog
> --
> There are not enough slots available in the system to satisfy the 65 slots
> that were requested by the application:
>  /home/mishima/mis/openmpi/demos/myprog
> 
> Either request fewer slots for your application, or make more slots
> available
> for use.
> --
> <<< HANG HERE!! >>>
> Abort is in progress...hit ctrl-c again within 5 seconds to forcibly
> terminate
> 
> I found this behavior when I happened to input wrong procs. With less than
> 4
> nodes or rsh - namely unmanaged state, it works. I'm afraid to say I have
> no
> idea how to resolve it. I hope you could fix the problem.
> 
> Tetsuya
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Searchable archives: 
> http://www.open-mpi.org/community/lists/devel/2014/04/index.php

[OMPI devel] One more v1.8 warning

[Ralph Castain]

memheap_buddy.c:93:5: warning: "__SIZEOF_LONG__" is not defined

[OMPI devel] v1.8 warnings

[Ralph Castain]

Would the respective parties please clean these up for v1.8.1?

common_verbs_find_ports.c:164: warning: 'transport_name_to_str' defined but not 
used
btl_openib_component.c: In function 'btl_openib_component_init':
btl_openib_component.c:2696: warning: unused variable 'qp_index'


In file included from btl_vader_module.c:29:
btl_vader_fbox.h:51: warning: type qualifiers ignored on function return type
In file included from btl_vader_component.c:35:
btl_vader_fbox.h:51: warning: type qualifiers ignored on function return type
In file included from btl_vader_send.c:29:
btl_vader_fbox.h:51: warning: type qualifiers ignored on function return type
In file included from btl_vader_sendi.c:30:
btl_vader_fbox.h:51: warning: type qualifiers ignored on function return type


Thanks
Ralph