Right ok, I remember now.
Thanks!
On Dec 3, 2007, at 12:38 PM, Aurelien Bouteiller wrote:
You asked the exact same question in Paris, so I bet you don't
remember the discussions :)
We can not only use a callback on request completion (actually there
is already one, req_free is called anytime
You asked the exact same question in Paris, so I bet you don't
remember the discussions :)
We can not only use a callback on request completion (actually there
is already one, req_free is called anytime a request completes and can
be used to that purpose). We need to know wether the reques
Aurelien --
I confess to forgetting some of the Paris discussion. :-\
Could the same effect of these pointers also be effected by having a
completion callback function pointer on the request? Or do you need
more than that?
On Nov 29, 2007, at 6:37 PM, Aurelien Bouteiller wrote:
This pa
I would find this a useful feature. I haven't played with the diff so
I can't comment on it, but the idea of it sounds good to me.
Cheers,
Josh
On Nov 29, 2007, at 6:37 PM, Aurelien Bouteiller wrote:
This patch introduces customisable wait/test for requests as
discussed at the face-to-face
This patch introduces customisable wait/test for requests as discussed
at the face-to-face ompi meeting in Paris.
A new global structure (ompi_request_functions) holding all the
pointers to the wait/test functions have been added.
ompi_request_wait* and ompi_request_test* have been #defined
For message logging purpose, we need to interface with wait_any,
wait_some, test, test_any, test_some, test_all. It is not possible to
use PMPI for this purpose. During the face-to-face meeting in Paris
(5-12 october 2007) we discussed this issue and came to the
conclusion that the best way
