linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH rdma-next v5 0/3] Track memory allocation with restrack DB help (Part II)
@ 2020-11-17  7:01 Leon Romanovsky
  2020-11-27 16:03 ` Jason Gunthorpe
  0 siblings, 1 reply; 2+ messages in thread
From: Leon Romanovsky @ 2020-11-17  7:01 UTC (permalink / raw)
  To: Doug Ledford, Jason Gunthorpe
  Cc: Leon Romanovsky, Ariel Levkovich, Gal Pressman, Leon Romanovsky,
	linux-kernel, linux-rdma, Mark Zhang, Yishai Hadas

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

 drivers/infiniband/core/core_priv.h           | 25 ++++++-------------
 drivers/infiniband/core/counters.c            |  2 +-
 drivers/infiniband/core/restrack.c            | 12 +++++++--
 drivers/infiniband/core/uverbs_cmd.c          |  4 +--
 drivers/infiniband/core/uverbs_std_types_mr.c |  4 +++
 drivers/infiniband/core/uverbs_std_types_qp.c |  4 +--
 drivers/infiniband/core/verbs.c               | 11 ++++----
 drivers/infiniband/hw/mlx4/qp.c               |  5 ++++
 drivers/infiniband/hw/mlx5/qp.c               |  2 +-
 include/rdma/ib_verbs.h                       | 10 ++++++--
 include/rdma/restrack.h                       | 24 ++++++++++++++++++
 11 files changed, 70 insertions(+), 33 deletions(-)

--
2.28.0


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH rdma-next v5 0/3] Track memory allocation with restrack DB help (Part II)
  2020-11-17  7:01 [PATCH rdma-next v5 0/3] Track memory allocation with restrack DB help (Part II) Leon Romanovsky
@ 2020-11-27 16:03 ` Jason Gunthorpe
  0 siblings, 0 replies; 2+ messages in thread
From: Jason Gunthorpe @ 2020-11-27 16:03 UTC (permalink / raw)
  To: Leon Romanovsky
  Cc: Doug Ledford, Leon Romanovsky, Ariel Levkovich, Gal Pressman,
	Leon Romanovsky, linux-kernel, linux-rdma, Mark Zhang,
	Yishai Hadas

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-11-27 16:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-17  7:01 [PATCH rdma-next v5 0/3] Track memory allocation with restrack DB help (Part II) Leon Romanovsky
2020-11-27 16:03 ` Jason Gunthorpe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).