>> > From: Michael S. Tsirkin [mailto:[EMAIL PROTECTED] >> > Sent: Tuesday, July 12, 2005 3:15 PM >> > >> > Quoting r. Sean Hefty <[EMAIL PROTECTED]>: >> > > >> > > I believe that this is purely a userspace issue. I can't see why >> > > using a mutex wouldn't work, but I believe that get_event() currently >> > > blocks waiting for an event. >> > > >> > > Note that get_event() may be reporting events associated with an >> > > object other than the one being destroyed. >> > >> > Maybe, create a special kind of event after the object has been destroyed? >> >> Adding such an event in effect makes destruction asynchronous - the user must >> wait until the destroy event before freeing their context. > >I think you can make this part of destroy: this event simply >solves a deadlock where get_event is blocked so you cant destroy >an object. > >destroy >take mutex >get_event(non blocking) >free mutex
I'm not sure that a destroy event helps here either. I don't think that anything prevents a user from calling get_event() from multiple threads. Also, currently get_event() is not tied to a specific object. - Sean _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
