What's next on this ticket? It's supposed to be a blocker. Again, the
issue is that osu_bw deluges a receiver with rendezvous messages, but
the receiver does not have enough eager frags to acknowledge them all.
We see this now that the sizing of the mmap file has changed and there's
less hea
Done.
On Apr 3, 2009, at 2:45 PM, Eugene Loh wrote:
Do I need to buy someone a beer to get access to the test suites?
[eloh@milliways]$ svn co https://svn.open-mpi.org/svn/ompi/trunk
[... successful ...]
[eloh@milliways]$ svn co
https://svn.open-mpi.org/svn/ompi-tests/trunk/intel_tests
svn: PR
Do I need to buy someone a beer to get access to the test suites?
[eloh@milliways]$ svn co https://svn.open-mpi.org/svn/ompi/trunk
[... successful ...]
[eloh@milliways]$ svn co
https://svn.open-mpi.org/svn/ompi-tests/trunk/intel_tests
svn: PROPFIND request failed on '/svn/ompi-tests/trunk/intel
Correct. We use the event library (a customized drop of libevent) for
three main things:
1. monitoring file descriptors
2. scheduling timed callbacks (i.e., you can set a callback to fire at
some point in the future)
3. monitoring signals
You can register a callback to occur when these eve
Do you mean the code in OPAL/event? If so, it's a customised libevent. I've
seen it used in OpenMPI to poll/select open sockets, it allows the
programmer register their own callback functions for when this happens. Just
ignore me if this wasn't what you were asking about though :-)
Tim
2009/4/3 E
What is the purpose of the event library? I'd happily RTFM if someone
could point me in that direction! :^)
I'm guessing it's to check occasionally for "unexpected events", but if
someone could confirm/deny and flesh that picture out a little, I'd
appreciate it.
