From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
Aharon Landau <aharonl@mellanox.com>,
Eli Cohen <eli@mellanox.com>,
Jack Morgenstein <jackm@dev.mellanox.co.il>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Maor Gottlieb <maorg@mellanox.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
Roland Dreier <roland@purestorage.com>
Subject: [PATCH rdma-next 00/18] Refactor mlx5_ib_create_qp (Part II)
Date: Thu, 23 Apr 2020 22:02:45 +0300 [thread overview]
Message-ID: <20200423190303.12856-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@mellanox.com>
Hi,
This is second part of refactor mlx5_ib_create_qp() series [1] with one
extra fix from Aharon.
It is based on [1].
Thanks
[1] https://lore.kernel.org/lkml/20200420151105.282848-1-leon@kernel.org
Aharon Landau (1):
RDMA/mlx5: Verify that QP is created with RQ or SQ
Leon Romanovsky (17):
RDMA/mlx5: Delete unsupported QP types
RDMA/mlx5: Store QP type in the vendor QP structure
RDMA/mlx5: Promote RSS RAW QP attribute check in higher level
RDMA/mlx5: Combine copy of create QP command in RSS RAW QP
RDMA/mlx5: Remove second user copy in create_user_qp
RDMA/mlx5: Rely on existence of udata to separate kernel/user flows
RDMA/mlx5: Delete impossible inlen check
RDMA/mlx5: Globally parse DEVX UID
RDMA/mlx5: Separate XRC_TGT QP creation from common flow
RDMA/mlx5: Separate to user/kernel create QP flows
RDMA/mlx5: Reduce amount of duplication in QP destroy
RDMA/mlx5: Group all create QP parameters to simplify in-kernel
interfaces
RDMA/mlx5: Promote RSS RAW QP flags check to higher level
RDMA/mlx5: Handle udate outlen checks in one place
RDMA/mlx5: Copy response to the user in one place
RDMA/mlx5: Remove redundant destroy QP call
RDMA/mlx5: Consolidate into special function all create QP calls
drivers/infiniband/hw/mlx5/mlx5_ib.h | 22 +-
drivers/infiniband/hw/mlx5/odp.c | 3 +-
drivers/infiniband/hw/mlx5/qp.c | 989 ++++++++++++++++-----------
3 files changed, 586 insertions(+), 428 deletions(-)
--
2.25.3
reply other threads:[~2020-04-23 19:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200423190303.12856-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=aharonl@mellanox.com \
--cc=dledford@redhat.com \
--cc=eli@mellanox.com \
--cc=jackm@dev.mellanox.co.il \
--cc=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=roland@purestorage.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
Powered by JetHome