From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@nvidia.com>,
Ariel Levkovich <lariel@mellanox.com>,
Gal Pressman <galpress@amazon.com>,
Leon Romanovsky <leonro@mellanox.com>,
<linux-kernel@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
Mark Zhang <markz@nvidia.com>, Yishai Hadas <yishaih@nvidia.com>
Subject: Re: [PATCH rdma-next v5 0/3] Track memory allocation with restrack DB help (Part II)
Date: Fri, 27 Nov 2020 12:03:45 -0400 [thread overview]
Message-ID: <20201127160345.GA667848@nvidia.com> (raw)
In-Reply-To: <20201117070148.1974114-1-leon@kernel.org>
On Tue, Nov 17, 2020 at 09:01:45AM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Changelog:
> v5:
> * Reorder patches to postpone changes in rdma_restrack_add to be in next series.
> v4: https://lore.kernel.org/linux-rdma/20201104144008.3808124-1-leon@kernel.org/
> * Rebased on latest for-upstream, all that time the patches were in
> our regression and didn't introduce any issues.
> * Took first five patches that hadn't any comments
> v3: https://lore.kernel.org/lkml/20200926101938.2964394-1-leon@kernel.org
> * Rebased on already accepted patches.
> * Added mlx4 special QPs to the list of not-tracked QPs (dropped previous mlx4 special QP patch).
> * Separated to two patches change in return value of cma_listen_* routines.
> * Changed commit messages and added Fixes as Jason requested.
> v2: https://lore.kernel.org/linux-rdma/20200907122156.478360-1-leon@kernel.org/
> * Added new patch to fix mlx4 failure on SR-IOV, it didn't have port set.
> * Changed "RDMA/cma: Delete from restrack DB after successful destroy" patch.
> v1: https://lore.kernel.org/lkml/20200830101436.108487-1-leon@kernel.org
> * Fixed rebase error, deleted second assignment of qp_type.
> * Rebased code on latests rdma-next, the changes in cma.c caused to change
> in patch "RDMA/cma: Delete from restrack DB after successful destroy".
> * Dropped patch of port assignment, it is already done as part of this
> series.
> * I didn't add @calller description, regular users should not use _named() funciton.
> v0: https://lore.kernel.org/lkml/20200824104415.1090901-1-leon@kernel.org
>
> ----------------------------------------------------------------------------------
>
> Leon Romanovsky (3):
> RDMA/core: Track device memory MRs
> RDMA/core: Allow drivers to disable restrack DB
> RDMA/restrack: Support all QP types
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2020-11-27 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 7:01 [PATCH rdma-next v5 0/3] Track memory allocation with restrack DB help (Part II) Leon Romanovsky
2020-11-17 7:01 ` [PATCH rdma-next v5 1/3] RDMA/core: Track device memory MRs Leon Romanovsky
2020-11-17 7:01 ` [PATCH rdma-next v5 2/3] RDMA/core: Allow drivers to disable restrack DB Leon Romanovsky
2020-11-17 7:01 ` [PATCH rdma-next v5 3/3] RDMA/restrack: Support all QP types Leon Romanovsky
2020-11-27 16:03 ` Jason Gunthorpe [this message]
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=20201127160345.GA667848@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=galpress@amazon.com \
--cc=lariel@mellanox.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=markz@nvidia.com \
--cc=yishaih@nvidia.com \
/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.