RE: [PATCH rdma-next v2 0/7] RDMA resource tracking

["Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>]

> On Mon, Jan 08, 2018 at 02:53:38PM -0600, Steve Wise wrote:
> > >
> > > Changelog:
> > > v1->v2:
> > >  * Rebased on latest rdma/for-next
> > >  * Replaced mutex lock which protect linked lists to be RW semaphore.
> > >    It has no impact on current implementation, because there is only
one
> > >    reader (nldev) and it is serialized. However better to be prepared
> > >    for multiple readers from the beginning.
> > >  * Added reinitialization next QP entry logic to ensure that it exists
> > >    and didn't vanish during fill_req_qp() work.
> > > v0->v1:
> > >  * Dropped RFC
> > >  * Separated to thre series, one for for-rc, and two for-next.
> >
> > Hey Leon,
> >
> > This series looks good to me.
> >
> > Reviewed-by: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
> >
> 
> Thanks a lot.>

You're welcome!  I'm planning on using this as a starting point for
qp/cq/connection state dumps for iw_cxgb4 objects.  This allows gathering
key state when debugging stalls/hangs/etc.  So I'm hoping this can get
integrated soon, so we can add to it going forward.

Steve.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html