Did you ever run 'git blame' to find out why some part of MPICH does
what it does, only to find the commit responsible was 6a1cbdcfc42 "Added
all components in the right places."? I'm personally surprised how
often I care about changes made more than 8 years ago.
If you, like me, sometimes find yourself needing more history, you can
now -- ta-da -- consult http://git.mpich.org/mpich-CVS.git/
When we converted from CVS to subversion back in 2007, the conversion
tools could not handle some oddities in our CVS repository,
necessitating a wipeoput of history. I guess in the intervening 8 years
the conversion tools are more tolerant (once you repack your repository
to remove any modules-containing-modules).
This is still a disconnected tree from today's MPICH development, but
now you can browse the old history with the tools we are familiar with
today (no need to build/install cvsps or remember old CVS commands).
==rob
--
Rob Latham
Mathematics and Computer Science Division
Argonne National Lab, IL USA
^__^
Many thanks! Pavan
On Wed, Jul 1, 2015 at 7:59 PM, Balaji, Pavan <balaji(a)anl.gov> wrote:
>
> We are not very good at names. :-)
>
> "persist" is for a "persistent daemon", which makes no sense, since sshd
> is a persistent too.
>
> "bss" stands for "bootstrap server", and the name conflict is
> unfortunate.
>
> -- Pavan
>
> From: unix haha
> Reply-To: "devel(a)mpich.org"
> Date: Tuesday, June 30, 2015 at 9:35 PM
> To: "devel(a)mpich.org"
> Subject: Re: [mpich-devel] about MPI hydra process management
>
> Thanks, Balaji.
>
> I took a quick look on persist bootstrap. It seems what I want and I will
> try it.
>
> one thing puzzles me is what's "persist" means here for hydra. what's
> means for hydra_bss_persist in Makefile.mk under hydra/tools/bootstrap/?
> the bss is the .bss section in executable file?
>
> Thanks!
>
> On Wed, Jul 1, 2015 at 7:29 AM, Balaji, Pavan <balaji(a)anl.gov> wrote:
>
>>
>> Hydra supports a bunch of daemon processes, including ssh. There is a
>> daemon process included with MPICH called "persist", which you could use
>> for this purpose, but it's not really maintained. You could try it.
>>
>> -- Pavan
>>
>> From: unix haha
>> Reply-To: "devel(a)mpich.org"
>> Date: Tuesday, June 30, 2015 at 6:18 PM
>> To: "devel(a)mpich.org"
>> Subject: [mpich-devel] about MPI hydra process management
>>
>> Hi, all:
>>
>> I'm working on port the MPICH2 3.1.4 to an embedded environment. I
>> met some problems for hydra process management, Could anyone help me?
>>
>> 1. For the old MPD, before the mpirun, there's a daemon process
>> running on all computer nodes. But I don't see what's hydra's daemon
>> process in the current MPI document. Could you give me some hints?
>>
>> 2. As we run the MPICH2 in a resource constraint environment, the
>> SSH or the other linux-based launcher may not be used. Does it exist any
>> simple launcher running on the computer nodes before the mpiexec?
>>
>> 3. What's my understanding for hydra is: once the Launcher process
>> running on all computer nodes, I can use the mpiexec on the control node to
>> start the parallel jobs? If so, the problem is: Could I start the Launcher
>> process manually if there's no linux-based launcher?
>>
>> Thanks!
>>
>> _______________________________________________
>> To manage subscription options or unsubscribe:
>> https://lists.mpich.org/mailman/listinfo/devel
>>
>
>
> _______________________________________________
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/devel
>
We are not very good at names. :-)
"persist" is for a "persistent daemon", which makes no sense, since sshd is a persistent too.
"bss" stands for "bootstrap server", and the name conflict is unfortunate.
-- Pavan
From: unix haha
Reply-To: "devel(a)mpich.org<mailto:[email protected]>"
Date: Tuesday, June 30, 2015 at 9:35 PM
To: "devel(a)mpich.org<mailto:[email protected]>"
Subject: Re: [mpich-devel] about MPI hydra process management
Thanks, Balaji.
I took a quick look on persist bootstrap. It seems what I want and I will try it.
one thing puzzles me is what's "persist" means here for hydra. what's means for hydra_bss_persist in Makefile.mk under hydra/tools/bootstrap/? the bss is the .bss section in executable file?
Thanks!
On Wed, Jul 1, 2015 at 7:29 AM, Balaji, Pavan <balaji(a)anl.gov<mailto:[email protected]>> wrote:
Hydra supports a bunch of daemon processes, including ssh. There is a daemon process included with MPICH called "persist", which you could use for this purpose, but it's not really maintained. You could try it.
-- Pavan
From: unix haha
Reply-To: "devel(a)mpich.org<mailto:[email protected]>"
Date: Tuesday, June 30, 2015 at 6:18 PM
To: "devel(a)mpich.org<mailto:[email protected]>"
Subject: [mpich-devel] about MPI hydra process management
Hi, all:
I'm working on port the MPICH2 3.1.4 to an embedded environment. I met some problems for hydra process management, Could anyone help me?
1. For the old MPD, before the mpirun, there's a daemon process running on all computer nodes. But I don't see what's hydra's daemon process in the current MPI document. Could you give me some hints?
2. As we run the MPICH2 in a resource constraint environment, the SSH or the other linux-based launcher may not be used. Does it exist any simple launcher running on the computer nodes before the mpiexec?
3. What's my understanding for hydra is: once the Launcher process running on all computer nodes, I can use the mpiexec on the control node to start the parallel jobs? If so, the problem is: Could I start the Launcher process manually if there's no linux-based launcher?
Thanks!
_______________________________________________
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/devel
Thanks, Balaji.
I took a quick look on persist bootstrap. It seems what I want and I will
try it.
one thing puzzles me is what's "persist" means here for hydra. what's means
for hydra_bss_persist in Makefile.mk under hydra/tools/bootstrap/? the bss
is the .bss section in executable file?
Thanks!
On Wed, Jul 1, 2015 at 7:29 AM, Balaji, Pavan <balaji(a)anl.gov> wrote:
>
> Hydra supports a bunch of daemon processes, including ssh. There is a
> daemon process included with MPICH called "persist", which you could use
> for this purpose, but it's not really maintained. You could try it.
>
> -- Pavan
>
> From: unix haha
> Reply-To: "devel(a)mpich.org"
> Date: Tuesday, June 30, 2015 at 6:18 PM
> To: "devel(a)mpich.org"
> Subject: [mpich-devel] about MPI hydra process management
>
> Hi, all:
>
> I'm working on port the MPICH2 3.1.4 to an embedded environment. I
> met some problems for hydra process management, Could anyone help me?
>
> 1. For the old MPD, before the mpirun, there's a daemon process
> running on all computer nodes. But I don't see what's hydra's daemon
> process in the current MPI document. Could you give me some hints?
>
> 2. As we run the MPICH2 in a resource constraint environment, the
> SSH or the other linux-based launcher may not be used. Does it exist any
> simple launcher running on the computer nodes before the mpiexec?
>
> 3. What's my understanding for hydra is: once the Launcher process
> running on all computer nodes, I can use the mpiexec on the control node to
> start the parallel jobs? If so, the problem is: Could I start the Launcher
> process manually if there's no linux-based launcher?
>
> Thanks!
>
> _______________________________________________
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/devel
>
