[openib-general] Re: [PATCH 3/3] iWARP CM - iWARP Connection Manager

2006-03-24 Thread Tom Tucker
On Thu, 2006-03-23 at 09:46 -0800, Sean Hefty wrote: > Would something more like this work? This waits for the CLOSE event to be > processed before releasing the last reference, which is what I think you were > going for. > > >+struct iwcm_id_private { > >+struct iw_cm_id id; > >+ > >+un

Re: [openib-general] Re: [PATCH 3/3] iWARP CM - iWARP Connection Manager

2006-03-22 Thread Steve Wise
| What's needed is a simple way to know that a provider will not invoke a callback | referencing an invalid context. This code tries to push this responsibility to | the owner of the context (i.e. here), rather than down into the provider, where | it really belongs. | | Somewhere the provider i

[openib-general] Re: [PATCH 3/3] iWARP CM - iWARP Connection Manager

2006-03-21 Thread Sean Hefty
Thanks for putting up with the comments. :) This is getting close; I think that we might be able to get it just a little bit simpler -- something like what's shown below where we key destruction only off of the refcount, and always perform it in ib_destroy_cm_id(). The one area that I'm stil