From: Jason Gunthorpe <jgg@nvidia.com>
To: Weihang Li <liweihang@huawei.com>
Cc: <dledford@redhat.com>, <leon@kernel.org>,
<linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>
Subject: Re: [PATCH for-next] RDMA/hns: Get udp sport num dynamically instead of using a fixed value
Date: Mon, 31 Aug 2020 12:25:57 -0300 [thread overview]
Message-ID: <20200831152557.GA628533@nvidia.com> (raw)
In-Reply-To: <1598002289-8611-1-git-send-email-liweihang@huawei.com>
On Fri, Aug 21, 2020 at 05:31:29PM +0800, Weihang Li wrote:
> The UDP source port number in RoCE v2 is used to create entropy for network
> routers (ECMP), load balancers and 802.3ad link aggregation switching that
> are not aware of RoCE IB headers. Considering that the IB core has achieved
> a new interface to get a hashed value of it，the fixed value of it in QPC
> and UD WQE in hns driver could be fixed and the port number is to be set
> dynamically now.
>
> For QPC of RC, the value could be hashed from flow_lable if the user pass
> it in or from remote qpn and local qpn. For WQE of UD, it is set according
> to fl or as a random value.
>
> Signed-off-by: Weihang Li <liweihang@huawei.com>
> ---
> drivers/infiniband/hw/hns/hns_roce_ah.c | 18 ++++++++++++++++++
> drivers/infiniband/hw/hns/hns_roce_device.h | 23 ++++++++++++-----------
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 13 +++++++++++--
> include/rdma/ib_verbs.h | 1 +
> 4 files changed, 42 insertions(+), 13 deletions(-)
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2020-08-31 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 9:31 [PATCH for-next] RDMA/hns: Get udp sport num dynamically instead of using a fixed value Weihang Li
2020-08-31 15:25 ` Jason Gunthorpe [this message]
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=20200831152557.GA628533@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liweihang@huawei.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).