Closed ompiteam closed 7 years ago
Imported from trac issue 1273. Created by rolfv on 2008-04-17T15:26:54, last modified: 2008-07-07T17:29:56
Trac comment by jsquyres on 2008-04-17 16:08:57:
Per some off-ticket discussion, this is ''possibly'' a problem with libevent itself (but it could also be a problem with Solaris event ports).
Unfortunately, we don't really have time to look into this at the moment, so we're going to just temporarily disable Solaris event ports in libevent. We're leaving this ticket here as future documentation so that we can come back to it someday (post 1.3). Note: if it really is a problem in libevent, we should get it fixed upstream.
Disabling Solaris event ports requires a configure change, so I'll hold off committing until tonight.
Trac comment by jsquyres on 2008-04-17 19:14:44:
(In [18199]) Temporarily disable Solaris ports support in libevent. Refs https://svn.open-mpi.org/trac/ompi/ticket/1273
Trac comment by rolfv on 2008-07-07 17:29:56:
Here are a few links that have some information about the performance of /dev/poll in Solaris and the use of event ports in libevent.
http://blogs.sun.com/dap/entry/libevent_and_solaris_event_ports
http://blogs.sun.com/dap/entry/event_ports_and_performance_take
We've fixed this to the extent possible
We have observed hangs when running applications on Solaris. It appears that this is because of the use of event ports.
Here is an example the stack trace when it hangs.
Here is it running with an env var set so we can see the type of polling being used.
And if we change it to use devpoll, poll, or select, it works.
And here is case of disabling event port, and letting the library pick next available.
We only saw this on our debuggable builds. We did not see it with our optimized builds. It is not clear what difference in the configure is triggering this.
Here is the configure line that triggers the problem.