Re: [OMPI devel] RES: v pml question

2008-01-29 Thread Aurélien Bouteiller
I just agree with Josh. We though about it a bit, and nothing should  
prevent to use both.


Aurelien
Le 29 janv. 08 à 15:01, Josh Hursey a écrit :


At the moment I do not plan on joining the crcpw and v_protocol.

However those two components may currently work just fine together.
They are both designed to wrap around whatever the 'selected' PML
happens to be. If you tried to do this, I would expect the PML call
stack to look something like the following:
PML_SEND -> v_protocol -> crcpw -> ob1/cm

But since I have not tried this out I cannot say for sure. Let us know
if you have any problems.

Cheers,
Josh

On Jan 23, 2008, at 4:55 PM, Leonardo Fialho wrote:


I'm testing the v protocol just now. Anybody have plans to do a
message
wrapper mixing crcpw and v_protocol?

Leonardo Fialho
University Autonoma of Barcelona


___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel


___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel





Re: [OMPI devel] RES: v pml question

2008-01-29 Thread Josh Hursey

At the moment I do not plan on joining the crcpw and v_protocol.

However those two components may currently work just fine together.  
They are both designed to wrap around whatever the 'selected' PML  
happens to be. If you tried to do this, I would expect the PML call  
stack to look something like the following:

PML_SEND -> v_protocol -> crcpw -> ob1/cm

But since I have not tried this out I cannot say for sure. Let us know  
if you have any problems.


Cheers,
Josh

On Jan 23, 2008, at 4:55 PM, Leonardo Fialho wrote:

I'm testing the v protocol just now. Anybody have plans to do a  
message

wrapper mixing crcpw and v_protocol?

Leonardo Fialho
University Autonoma of Barcelona


___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel




Re: [OMPI devel] RES: v pml question

2008-01-23 Thread Aurélien Bouteiller

Hi,

Actually it might already work. We never tried yet but nothing should  
prevent it.


The symlinks are necessary to trick the autogen and configure stages.  
This is required to avoid code replication from autogen.sh. If you  
look carefully you will see that the simlinks are created only inside  
the build directory, and not in the source directory. Thus it does not  
help to add them to the trunk.


Aurelien

Le 23 janv. 08 à 16:55, Leonardo Fialho a écrit :

I'm testing the v protocol just now. Anybody have plans to do a  
message

wrapper mixing crcpw and v_protocol?

Leonardo Fialho
University Autonoma of Barcelona

-Mensagem original-
De: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org]  
Em nome

de Jeff Squyres
Enviada em: miércoles, 23 de enero de 2008 22:45
Para: Open Developers
Assunto: [OMPI devel] v pml question

Just curious: what are the "mca" and "vprotocol" symlinks to "." for  
in the

v/vprotocol directory for?

If they're necessary, can they be committed to svn?  If they're not
necessary, can they be removed?

--
Jeff Squyres
Cisco Systems

___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel


___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel