Roland Dreier wrote:
Sean> I think that the issue that Arlin is hitting is that once he
Sean> calls blah_get_event() he doesn't have an easy way to
Sean> release the thread. This may turn out to be a uCM / uAT
Sean> issue, and not a verbs issue.
I thought about this some more. I think the real issue is probably
that the app is sleeping blah_get_event() on a blocking fd. If the
app doesn't want to block in that function forever, then it should use
poll() with a wake-up pipe() fd as well as the event fd. (I'm also
not sure what's so bad about pthread_kill() as a wake-up)
- R.
The application (udapl completion thread) is polling on the FD so it is
very easy to add a pipe() fd to wakeup. I was just expecting the close_fd in
ibv_close_device() to wakeup the poll (or blocking get_event) so I could exit
the thread without a pipe or a kill.
pthread_kill requires me to add a sig_handler to catch the signal and since
uDAPL is a library, there is a chance of uDAPL replacing a signal handler already
setup by the application for the process group.
-arlin
|
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
