From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Doug Ledford <dledford@redhat.com>,
Lior Nahmanson <liorna@nvidia.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Meir Lichtinger <meirl@nvidia.com>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>
Subject: Re: [PATCH rdma-next v1 2/3] RDMA/mlx5: Separate DCI QP creation logic
Date: Wed, 23 Jun 2021 09:03:38 +0300 [thread overview]
Message-ID: <YNLOurv1BXrlpsha@unreal> (raw)
In-Reply-To: <20210622184556.GA2596427@nvidia.com>
On Tue, Jun 22, 2021 at 03:45:56PM -0300, Jason Gunthorpe wrote:
> On Mon, Jun 21, 2021 at 10:06:15AM +0300, Leon Romanovsky wrote:
> > From: Lior Nahmanson <liorna@nvidia.com>
> >
> > This patch isolates DCI QP creation logic to separate function, so this
> > change will reduce complexity when adding new features to DCI QP without
> > interfering with other QP types.
> >
> > The code was copied from create_user_qp() while taking only DCI relevant bits.
> >
> > Reviewed-by: Meir Lichtinger <meirl@nvidia.com>
> > Signed-off-by: Lior Nahmanson <liorna@nvidia.com>
> > Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> > drivers/infiniband/hw/mlx5/qp.c | 157 ++++++++++++++++++++++++++++++++
> > 1 file changed, 157 insertions(+)
> >
> > diff --git a/drivers/infiniband/hw/mlx5/qp.c b/drivers/infiniband/hw/mlx5/qp.c
> > index 7a5f1eba60e3..65a380543f5a 100644
> > +++ b/drivers/infiniband/hw/mlx5/qp.c
> > @@ -1974,6 +1974,160 @@ static int create_xrc_tgt_qp(struct mlx5_ib_dev *dev, struct mlx5_ib_qp *qp,
> > return 0;
> > }
> >
> > +static int create_dci(struct mlx5_ib_dev *dev, struct ib_pd *pd,
> > + struct mlx5_ib_qp *qp,
> > + struct mlx5_create_qp_params *params)
> > +{
>
> This is a huge amount of copying just to add 4 lines, why?
>
> There must be a better way to do this qp stuff.
>
> Why not put more stuff in _create_user_qp()?
Lior proposed it in original patch, but I didn't like it. It caused to
mix of various QP types and maze of "if () else ()" that are not applicable
one to another.
The huge _create_user_qp() is the reason why create_dci() is not small,
we simply had hard time to understand if specific HW bit is needed or
not in DCI flow.
My goal is to have small per-QP type specific functions that calls
to simple functions for very narrow scope.
Something like that:
static int create_dci(...)
{
...
configure_send_cq(..)
configure_recv_sq(..)
configure_srq(...)
...
}
static int create_user_qp(...)
{
...
configure_send_cq(..)
configure_recv_sq(..)
configure_srq(...)
...
}
Thanks
>
> Jason
next prev parent reply other threads:[~2021-06-23 6:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 7:06 [PATCH rdma-next v1 0/3] Add ConnectX DCS offload support Leon Romanovsky
2021-06-21 7:06 ` [PATCH mlx5-next v1 1/3] net/mlx5: Add DCS caps & fields support Leon Romanovsky
2021-06-21 7:06 ` [PATCH rdma-next v1 2/3] RDMA/mlx5: Separate DCI QP creation logic Leon Romanovsky
2021-06-22 18:45 ` Jason Gunthorpe
2021-06-23 6:03 ` Leon Romanovsky [this message]
2021-06-21 7:06 ` [PATCH rdma-next v1 3/3] RDMA/mlx5: Add DCS offload support Leon Romanovsky
2021-07-16 15:42 ` [PATCH rdma-next v1 0/3] Add ConnectX " Jason Gunthorpe
2021-07-18 10:38 ` Leon Romanovsky
2021-07-20 18:18 ` Jason Gunthorpe
2021-07-21 4:34 ` Leon Romanovsky
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=YNLOurv1BXrlpsha@unreal \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=liorna@nvidia.com \
--cc=meirl@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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).