All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Cc: 'Doug Ledford' <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	'Jason Gunthorpe' <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	'RDMA mailing list'
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	'Mark Bloch' <markb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH rdma-next v2 0/7] RDMA resource tracking
Date: Tue, 9 Jan 2018 09:53:44 +0200	[thread overview]
Message-ID: <20180109075344.GD6823@mtr-leonro.local> (raw)
In-Reply-To: <0bdd01d388c2$c1d79380$4586ba80$@opengridcomputing.com>

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

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.>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-01-09  7:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02  8:18 [PATCH rdma-next v2 0/7] RDMA resource tracking Leon Romanovsky
     [not found] ` <20180102081832.5264-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-02  8:18   ` [PATCH rdma-next v2 1/7] RDMA/restrack: Add general infrastructure to track RDMA resources Leon Romanovsky
2018-01-02  8:18   ` [PATCH rdma-next v2 2/7] RDMA/core: Add helper function to create named QPs Leon Romanovsky
2018-01-02  8:18   ` [PATCH rdma-next v2 3/7] RDMA: Annotate create QP callers Leon Romanovsky
2018-01-02  8:18   ` [PATCH rdma-next v2 4/7] RDMA/core: Add resource tracking for create and destroy CQs Leon Romanovsky
2018-01-02  8:18   ` [PATCH rdma-next v2 5/7] RDMA/core: Add resource tracking for create and destroy PDs Leon Romanovsky
2018-01-02  8:18   ` [PATCH rdma-next v2 6/7] RDMA/nldev: Provide global resource utilization Leon Romanovsky
2018-01-02  8:18   ` [PATCH rdma-next v2 7/7] RDMA/nldev: Provide detailed QP information Leon Romanovsky
     [not found]     ` <20180102081832.5264-8-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-09 20:09       ` Jason Gunthorpe
     [not found]         ` <20180109200917.GF4518-uk2M96/98Pc@public.gmane.org>
2018-01-09 21:46           ` Parav Pandit
2018-01-10  7:17           ` Leon Romanovsky
     [not found]             ` <20180110071722.GF7368-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-10 22:56               ` Jason Gunthorpe
     [not found]                 ` <20180110225622.GQ4518-uk2M96/98Pc@public.gmane.org>
2018-01-10 23:28                   ` Steve Wise
2018-01-11  5:41                     ` Leon Romanovsky
     [not found]                       ` <20180111054141.GM7368-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-11 15:17                         ` Steve Wise
2018-01-11 15:47                           ` Leon Romanovsky
2018-01-11  5:37                   ` Leon Romanovsky
2018-01-08 20:53   ` [PATCH rdma-next v2 0/7] RDMA resource tracking Steve Wise
2018-01-09  7:53     ` Leon Romanovsky [this message]
     [not found]       ` <20180109075344.GD6823-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-09 15:24         ` Steve Wise

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180109075344.GD6823@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=markb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.