[Swift-devel] Falkon and Coaster support for MPI

Mihael Hategan hategan at mcs.anl.gov
Mon Jun 30 14:27:38 CDT 2008


On Mon, 2008-06-30 at 13:16 -0500, Ioan Raicu wrote:
> 
> Mihael Hategan wrote:
> > On Mon, 2008-06-30 at 12:57 -0500, Ioan Raicu wrote:
> >   
> > ...
> >
> > Thank you for the token. I didn't realize I needed one though.
> >   
> I thought this entire thread was about identifying where 
> (Coaster/Falkon) it makes the most sense to add MPI support, given 
> people are really busy, and we don't want to duplicate the effort.

s/where/whether/.

Then you said it's hard (using the "bad is bad" argument), and you
wouldn't do it, and I said I didn't think it was that hard, and perhaps
it could be reasonably done.

After which you mentioned that it may not be as hard as you thought (at
least 1 day of coding on your part), then later suggested that it still
shouldn't be done because a random student/staff would likely not be
able to do it in a few months.

Further down the line, you mentioned you'll give it a try, and then if
you fail after a week, I or Ben could take a stab at it.

I believe we agreed that BG is a nasty platform.

The issues:
1. You really don't have to do anything as far as I'm concerned,
especially if you think it's too much for the time you have.
2. You don't get to decide (by giving tokens or otherwise) by yourself
when/whether I or Ben should do things.
3. There is no effort duplication. Falkon is your PhD research project.
Coasters are what I/we officially develop as production software.

I would like to suggest that in the future, we keep falkon and coaster
discussions separate. The term "falkon/coasters" should probably only be
used to denote the glide-in concept, not as a reference to the
implementations.

Mihael





More information about the Swift-devel mailing list