From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.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: [PATCH rdma-next 0/6] Set flow_label and RoCEv2 UDP source port for datagram QP
Date: Wed, 18 Mar 2020 11:52:54 +0200 [thread overview]
Message-ID: <20200318095300.45574-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@mellanox.com>
From Mark:
This series provide flow label and UDP source port definition in RoCE v2.
Those fields are used to create entropy for network routes (ECMP), load
balancers and 802.3ad link aggregation switching that are not aware of
RoCE headers.
Thanks.
Mark Zhang (6):
net/mlx5: Enable SW-defined RoCEv2 UDP source port
RDMA/core: Add hash functions to calculate RoCEv2 flowlabel and UDP
source port
RDMA/mlx5: Define RoCEv2 udp source port when set path
RDMA/cma: Initialize the flow label of CM's route path record
RDMA/cm: Set flow label of recv_wc based on primary flow label
RDMA/mlx5: Set UDP source port based on the grh.flow_label
drivers/infiniband/core/cm.c | 7 +++
drivers/infiniband/core/cma.c | 23 ++++++++++
drivers/infiniband/hw/mlx5/ah.c | 21 ++++++++-
drivers/infiniband/hw/mlx5/main.c | 4 +-
drivers/infiniband/hw/mlx5/mlx5_ib.h | 4 +-
drivers/infiniband/hw/mlx5/qp.c | 30 ++++++++++---
.../net/ethernet/mellanox/mlx5/core/main.c | 39 ++++++++++++++++
include/linux/mlx5/mlx5_ifc.h | 5 ++-
include/rdma/ib_verbs.h | 44 +++++++++++++++++++
9 files changed, 164 insertions(+), 13 deletions(-)
--
2.24.1
next reply other threads:[~2020-03-18 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 9:52 Leon Romanovsky [this message]
2020-03-18 9:52 ` [PATCH mlx5-next 1/6] net/mlx5: Enable SW-defined RoCEv2 UDP source port Leon Romanovsky
2020-03-18 23:33 ` Saeed Mahameed
2020-03-19 6:05 ` Leon Romanovsky
2020-03-20 1:16 ` Saeed Mahameed
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=20200318095300.45574-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--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).