On Mar 19, 2012, at 3:35 PM, Alex Margolin wrote:
> I've removed put and get from mosix (feels good to cut down on code
> lines...), but now the question has to be asked:
> Threre are send and sendi (is sendi sufficient, or must i include send as
> well?)
send is sufficient. sendi is an optimi
I've removed put and get from mosix (feels good to cut down on code
lines...), but now the question has to be asked:
Threre are send and sendi (is sendi sufficient, or must i include send
as well?) for the outgoing, but what about the incoming?
How does a process request input? Do I poll for inco
You don't have to implement all the protocols. The default is send protocol,
and this is the minimum you have to implement. The RMA protocols (GET or PUT)
are optional, and are specified by setting specific bits in your BTL flag.
Regarding the TCP BTL, the two RMA operations are "fake", they are
My module is close to completion (though I need to fix other issues with
shared memory to begin testing, but that's a different thread).
I'm trying to understand how exactly are the fragments returned to the
application once they are received.
In btl_tcp.c the function mca_btl_tcp_get() seems t
On Mar 3, 2012, at 18:18 , Alex Margolin wrote:
> I've figured that what I really need is to write my own BTL component, rather
> then trying to manipulate the existing TCP one. I've started writing it using
> the 1.5.5rc3 tarball and some pdfs from 2006 I found on the website (anything
> else
I've figured that what I really need is to write my own BTL component,
rather then trying to manipulate the existing TCP one. I've started
writing it using the 1.5.5rc3 tarball and some pdfs from 2006 I found on
the website (anything else I can look at? TCP is much more complicated
then what I'
Give your btl progress function. It'll get called quite frequently.
Look at the "progress" section in btl.h. Progress threads don't work yet, but
the btl_progress function will get called by the PML quite frequently. It's
how BTL's like openib progress their outstanding message passing.
On
On 03/02/2012 04:33 PM, Jeffrey Squyres wrote:
Note that the OMPI 1.4.x series is about to be retired. If you're doing new
stuff, I'd advise you to be working with the Open MPI SVN trunk. In the trunk,
we've changed how we build libevent, so if you're adding to it, you probably
want to be w
Note that the OMPI 1.4.x series is about to be retired. If you're doing new
stuff, I'd advise you to be working with the Open MPI SVN trunk. In the trunk,
we've changed how we build libevent, so if you're adding to it, you probably
want to be working there for max forward-compatibility.
That
I added my poll2.c to config/ompi_setup_libevent.m4 next to poll.c and
was able to build successfully, but even if poll2() just (prints and)
calls poll() - I get the following error (btl is specified to avoid
loading my module at this time):
alex@singularity:~/huji/benchmarks/simple$ ~/huji/om
Hi,
I'm trying to replace the poll() function with mine (say poll2() in
poll2.c), and I got some building errors.
This is after I copied poll2.c into opal/events/ and added it in the
sources list in Makefile.am in that folder.
...
Making all in tools/wrappers
make[2]: Entering directory
`/hom
11 matches
Mail list logo
