netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Doug Ledford <dledford@redhat.com>,
	linux-rdma@vger.kernel.org, Maor Gottlieb <maorg@mellanox.com>,
	Mark Zhang <markz@mellanox.com>,
	netdev@vger.kernel.org, Saeed Mahameed <saeedm@mellanox.com>
Subject: Re: [PATCH rdma-next v3 0/8] Driver part of the ECE
Date: Wed, 27 May 2020 05:54:28 +0300	[thread overview]
Message-ID: <20200527025428.GG100179@unreal> (raw)
In-Reply-To: <20200526190419.GA18519@ziepe.ca>

On Tue, May 26, 2020 at 04:04:20PM -0300, Jason Gunthorpe wrote:
> On Tue, May 26, 2020 at 02:54:32PM +0300, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro@mellanox.com>
> >
> > Changelog:
> > v3:
> >  * Squashed patch "RDMA/mlx5: Advertise ECE support" into
> >  "RDMA/mlx5: Set ECE options during modify QP".
> > v2:
> > https://lore.kernel.org/linux-rdma/20200525174401.71152-1-leon@kernel.org
> >  * Rebased on latest wip/jgg-rdma-next branch, commit a94dae867c56
> >  * Fixed wrong setting of pm_state field in mlx5 conversion patch
> >  * Removed DC support for now
> > v1:
> > https://lore.kernel.org/linux-rdma/20200523132243.817936-1-leon@kernel.org
> >  * Fixed compatibility issue of "old" kernel vs. "new" rdma-core. This
> >    is handled in extra patch.
> >  * Improved comments and commit messages after feedback from Yishai.
> >  * Added Mark Z. ROB tags
> > v0:
> > https://lore.kernel.org/linux-rdma/20200520082919.440939-1-leon@kernel.org
> >
> >
> > Hi,
> >
> > This is driver part of the RDMA-CM ECE series [1].
> > According to the IBTA, ECE data is completely vendor specific, so this
> > series extends mlx5_ib create_qp and modify_qp structs with extra field
> > to pass ECE options to/from the application.
> >
> > Thanks
> >
> > [1]
> > https://lore.kernel.org/linux-rdma/20200413141538.935574-1-leon@kernel.org
> >
> > Leon Romanovsky (8):
> >   net/mlx5: Add ability to read and write ECE options
> >   RDMA/mlx5: Get ECE options from FW during create QP
> >   RDMA/mlx5: Set ECE options during QP create
> >   RDMA/mlx5: Use direct modify QP implementation
> >   RDMA/mlx5: Remove manually crafted QP context the query call
> >   RDMA/mlx5: Convert modify QP to use MLX5_SET macros
> >   RDMA/mlx5: Set ECE options during modify QP
> >   RDMA/mlx5: Return ECE data after modify QP
>
> It seems fine, can you add the one patch to the shared branch please

First patch is applied to the mlx5-next.

f55ece0e11c1 net/mlx5: Add ability to read and write ECE options

Thanks

>
> Thanks,
> Jason

  reply	other threads:[~2020-05-27  2:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 11:54 [PATCH rdma-next v3 0/8] Driver part of the ECE Leon Romanovsky
2020-05-26 11:54 ` [PATCH mlx5-next v3 1/8] net/mlx5: Add ability to read and write ECE options Leon Romanovsky
2020-05-26 19:04 ` [PATCH rdma-next v3 0/8] Driver part of the ECE Jason Gunthorpe
2020-05-27  2:54   ` Leon Romanovsky [this message]
2020-05-27 19:14 ` 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=20200527025428.GG100179@unreal \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=maorg@mellanox.com \
    --cc=markz@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@mellanox.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).