Ah - now that is easily fixed, without breaking the support for everyone
else. I'll commit the fix right away.
Thanks
Ralph
On Mon, Jun 22, 2009 at 11:12 AM, Iain Bason wrote:
> Ralph Castain wrote:
>
>> Yes, but look at orte/mca/plm/rsh/plm_rsh_module.c:
>>
>> /* ensure that only the ssh
(Thanks, Nick, for explaining that kind values are compiler-dependent. I
was too lazy to do that.)
Jeff Squyres wrote:
Given that I'll inevitably get the language wrong, can someone suggest
proper verbiage for this statement in the OMPI README:
- MPI_REAL16 and MPI_COMPLEX32 are only supporte
Ralph Castain wrote:
Yes, but look at orte/mca/plm/rsh/plm_rsh_module.c:
/* ensure that only the ssh plm is selected on the remote daemon */
var = mca_base_param_environ_variable("plm", NULL, NULL);
opal_setenv(var, "rsh", true, &env);
free(var);
This is done in "ssh_chi
Given that I'll inevitably get the language wrong, can someone suggest
proper verbiage for this statement in the OMPI README:
- MPI_REAL16 and MPI_COMPLEX32 are only supported on platforms where a
portable C datatype can be found that matches the Fortran type
REAL*16, both in size and bit r
On Jun 22 2009, Iain Bason wrote:
Jeff Squyres wrote:
Thanks for looking into this, David.
So if I understand that correctly, it means you have to assign all
literals in your fortran program with a "_16" suffix. I don't know if
that's standard Fortran or not.
Yes, it is.
Sorry - no, it
Yes, but look at orte/mca/plm/rsh/plm_rsh_module.c:
/* ensure that only the ssh plm is selected on the remote daemon */
var = mca_base_param_environ_variable("plm", NULL, NULL);
opal_setenv(var, "rsh", true, &env);
free(var);
This is done in "ssh_child", right before we fork_exec
Ralph Castain wrote:
I'm sorry, but this change is incorrect.
If you look in orte/mca/ess/base/ess_base_std_orted.c, you will see
that -all- orteds, regardless of how they are launched, open and
select the PLM.
I believe you are mistaken. Look in plm_base_launch_support.c:
/* Th
Jeff Squyres wrote:
Thanks for looking into this, David.
So if I understand that correctly, it means you have to assign all
literals in your fortran program with a "_16" suffix. I don't know if
that's standard Fortran or not.
Yes, it is.
Iain
Let us think about this some more. We'll try and reply later today.
--td
Ralph Castain wrote:
Had a chance to think about how this might be done, and looked at it
for awhile after getting home. I -think- I found a way to do it, but
there are a couple of caveats:
1. Len's point about oversub
I personally prefer the way it's now.
This way guaranties me total control over mapping and allocating slots.
When I am using rankfile mapper, I know exactly what and where I am putting,
OS can easily oversubscribe my CPU with unmapped by rankfile processes. I am
also not sure how it will effect us
10 matches
Mail list logo
