linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
	linux-rdma@vger.kernel.org, Yishai Hadas <yishaih@nvidia.com>
Subject: [PATCH rdma-next 0/5] Clean up rereg_mr handling
Date: Mon, 30 Nov 2020 09:58:34 +0200	[thread overview]
Message-ID: <20201130075839.278575-1-leon@kernel.org> (raw)

From: Leon Romanovsky <leonro@nvidia.com>

The mlx5 rereg_mr implementation is convoluted. Such code causes
to hard to spot bugs and even harder task - code review.

This series from Jason cleans that flow.

Thanks

Jason Gunthorpe (5):
  RDMA/uverbs: Tidy input validation of ib_uverbs_rereg_mr()
  RDMA/uverbs: Check ODP in ib_check_mr_access() as well
  RDMA/uverbs: Allow drivers to create a new HW object during rereg_mr
  RDMA/mlx5: Reorganize mlx5_ib_reg_user_mr()
  RDMA/mlx5: Fix error unwinds for rereg_mr

 drivers/infiniband/core/rdma_core.c           |  51 ++
 drivers/infiniband/core/uverbs_cmd.c          | 114 ++--
 drivers/infiniband/core/uverbs_std_types_mr.c |   2 +-
 drivers/infiniband/hw/hns/hns_roce_device.h   |   7 +-
 drivers/infiniband/hw/hns/hns_roce_mr.c       |  15 +-
 drivers/infiniband/hw/mlx4/mlx4_ib.h          |   8 +-
 drivers/infiniband/hw/mlx4/mr.c               |  16 +-
 drivers/infiniband/hw/mlx5/devx.c             |   2 +-
 drivers/infiniband/hw/mlx5/mlx5_ib.h          |  10 +-
 drivers/infiniband/hw/mlx5/mr.c               | 532 ++++++++++--------
 drivers/infiniband/hw/mlx5/odp.c              |  16 +-
 include/rdma/ib_verbs.h                       |  13 +-
 include/rdma/uverbs_types.h                   |   5 +
 13 files changed, 482 insertions(+), 309 deletions(-)

--
2.28.0


             reply	other threads:[~2020-11-30  7:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  7:58 Leon Romanovsky [this message]
2020-11-30  7:58 ` [PATCH rdma-next 1/5] RDMA/uverbs: Tidy input validation of ib_uverbs_rereg_mr() Leon Romanovsky
2020-11-30  7:58 ` [PATCH rdma-next 2/5] RDMA/uverbs: Check ODP in ib_check_mr_access() as well Leon Romanovsky
2020-11-30  7:58 ` [PATCH rdma-next 3/5] RDMA/uverbs: Allow drivers to create a new HW object during rereg_mr Leon Romanovsky
2020-11-30  7:58 ` [PATCH rdma-next 4/5] RDMA/mlx5: Reorganize mlx5_ib_reg_user_mr() Leon Romanovsky
2020-11-30  7:58 ` [PATCH rdma-next 5/5] RDMA/mlx5: Fix error unwinds for rereg_mr Leon Romanovsky
2020-12-07 19:33 ` [PATCH rdma-next 0/5] Clean up rereg_mr handling Jason Gunthorpe

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=20201130075839.278575-1-leon@kernel.org \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --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 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).