From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Steve Wise" Subject: RE: [PATCH rdma-next v2 0/7] RDMA resource tracking Date: Mon, 8 Jan 2018 14:53:38 -0600 Message-ID: <0bdd01d388c2$c1d79380$4586ba80$@opengridcomputing.com> References: <20180102081832.5264-1-leon@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20180102081832.5264-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> Content-Language: en-us Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: 'Leon Romanovsky' , 'Doug Ledford' , 'Jason Gunthorpe' Cc: 'RDMA mailing list' , 'Mark Bloch' List-Id: linux-rdma@vger.kernel.org > > 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 -- 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