On 4/5/06, Sean Hefty <[EMAIL PROTECTED]> wrote: > >I don't see the connection (since we only need de-register, let's just call > >it flush and be done with it), but fine. Please propose an API then. > > The issue that I see is that ib_sa_flush() requires ib_mad_flush(), but the > MAD > layer API doesn't have the problem that we're talking about. I dislike the > trickling effect that this fix has. > > I need to give more thought about an interface, and who will really use it. > For > example, the local_sa performs its own path record queries because of the need > to obtain multiple paths. The ib_multicast module now handles multicast > join/leave requests, and could be made to do its own queries. It may be > possible to remove some of the ib_sa APIs.
Can't you pass in a reference to the client module for registration, and then take a reference from the context of each request that is released after the callback unwinds? I thought Linux had module reference functions... - Fab _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
