Re: [O-MPI users] [Beowulf] MorphMPI based on fortran itf (was: MPI ABI)

2005-10-12 Thread Greg Lindahl
On Wed, Oct 12, 2005 at 07:06:54PM +0100, Ashley Pittman wrote: > As it turns out I'm in a position to measure this fairly easily, our MPI > sits on top of a library called libelan, this does all the tag matching > at a very low level, all MPI does is convert the communicator into a bit > pattern,

Re: [O-MPI users] [Beowulf] MorphMPI based on fortran itf (was: MPI ABI)

2005-10-12 Thread Greg Lindahl
On Wed, Oct 12, 2005 at 12:05:13PM +0100, Ashley Pittman wrote: > Thirdly is the performance issue, any MPI vendor worth his salt tries > very hard to reduce the number of function calls and library's between > the application and the network, adding another one is a step in the > wrong direction.

Re: [O-MPI users] [Beowulf] MorphMPI based on fortran itf

2005-10-12 Thread Toon Knapen
Robert G. Brown wrote: > Ashley Pittman writes: > >> Personnel I think a MPI ABI would be a good thing however this is not >> the way to do it. > > > And this is exactly right. Futhermore, we all know the right way to do > it. It is for a new governing body or consortium to be established (or

Re: [O-MPI users] [Beowulf] MorphMPI based on fortran itf

2005-10-12 Thread Toon Knapen
Ashley Pittman wrote: > The second problem is that of linking, most MPI vendors already have > MPI_Init in their own library, having another library with it's own > wrapper MPI_Init in it is going to lead to a whole world of pain to do > with dynamic linking and symbol resolution. This is not som