From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@mellanox.com>,
<linux-rdma@vger.kernel.org>,
Meir Lichtinger <meirl@mellanox.com>,
"Michael Guralnik" <michaelgur@mellanox.com>,
<netdev@vger.kernel.org>, Saeed Mahameed <saeedm@mellanox.com>
Subject: Re: [PATCH rdma-next 0/3] Create UMR with relaxed ordering
Date: Fri, 24 Jul 2020 15:48:32 -0300 [thread overview]
Message-ID: <20200724184832.GA3642406@nvidia.com> (raw)
In-Reply-To: <20200716105248.1423452-1-leon@kernel.org>
On Thu, Jul 16, 2020 at 01:52:45PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
>
> Hi,
>
> ConnectX-7 supports setting relaxed ordering read/write mkey attribute by UMR,
> indicated by new HCA capabilities, so extend mlx5_ib driver to configure
> UMR control segment based on those capabilities.
>
> Thanks
>
> Meir Lichtinger (3):
> RDMA/mlx5: ConnectX-7 new capabilities to set relaxed ordering by UMR
> RDMA/mlx5: Use MLX5_SET macro instead of local structure
> RDMA/mlx5: Set mkey relaxed ordering by UMR with ConnectX-7
These look OK, can you apply the first patch to the shared branch
please?
Jason
next prev parent reply other threads:[~2020-07-24 18:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 10:52 [PATCH rdma-next 0/3] Create UMR with relaxed ordering Leon Romanovsky
2020-07-16 10:52 ` [PATCH mlx5-next 1/3] RDMA/mlx5: ConnectX-7 new capabilities to set relaxed ordering by UMR Leon Romanovsky
2020-07-16 10:52 ` [PATCH rdma-next 2/3] RDMA/mlx5: Use MLX5_SET macro instead of local structure Leon Romanovsky
2020-07-16 10:52 ` [PATCH rdma-next 3/3] RDMA/mlx5: Set mkey relaxed ordering by UMR with ConnectX-7 Leon Romanovsky
2020-07-24 18:48 ` Jason Gunthorpe [this message]
2020-07-24 19:31 ` [PATCH rdma-next 0/3] Create UMR with relaxed ordering Leon Romanovsky
2020-07-27 14:47 ` 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=20200724184832.GA3642406@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=meirl@mellanox.com \
--cc=michaelgur@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).