From: Yanjun Zhu <yanjun.zhu@linux.dev>
To: "Saleem, Shiraz" <shiraz.saleem@intel.com>,
"liangwenpeng@huawei.com" <liangwenpeng@huawei.com>,
"liweihang@huawei.com" <liweihang@huawei.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"Ismail, Mustafa" <mustafa.ismail@intel.com>,
"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH 4/4] RDMA/rxe: Use the standard method to produce udp source port
Date: Wed, 5 Jan 2022 21:10:09 +0800 [thread overview]
Message-ID: <8ea540d1-ce89-0248-0bd4-444ca1267e84@linux.dev> (raw)
In-Reply-To: <898d7419-7e29-6258-a41e-2c62f251a1b6@linux.dev>
在 2022/1/5 8:33, Yanjun Zhu 写道:
> 在 2022/1/5 1:17, Saleem, Shiraz 写道:
>>> Subject: [PATCH 4/4] RDMA/rxe: Use the standard method to produce
>>> udp source
>>> port
>>>
>>> From: Zhu Yanjun <yanjun.zhu@linux.dev>
>>>
>>> Use the standard method to produce udp source port.
>>>
>>> Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
>>> ---
>>> drivers/infiniband/sw/rxe/rxe_verbs.c | 10 ++++++++++
>>> 1 file changed, 10 insertions(+)
>>>
>>> diff --git a/drivers/infiniband/sw/rxe/rxe_verbs.c
>>> b/drivers/infiniband/sw/rxe/rxe_verbs.c
>>> index 0aa0d7e52773..f30d98ad13cd 100644
>>> --- a/drivers/infiniband/sw/rxe/rxe_verbs.c
>>> +++ b/drivers/infiniband/sw/rxe/rxe_verbs.c
>>> @@ -469,6 +469,16 @@ static int rxe_modify_qp(struct ib_qp *ibqp,
>>> struct
>>> ib_qp_attr *attr,
>>> if (err)
>>> goto err1;
>>>
>>> + if (mask & IB_QP_AV) {
>>> + if (attr->ah_attr.ah_flags & IB_AH_GRH) {
>>> + u32 fl = attr->ah_attr.grh.flow_label;
>>> + u32 lqp = qp->ibqp.qp_num;
>>> + u32 rqp = qp->attr.dest_qp_num;
>>> +
>> Isn't the randomization for src_port done in rxe_qp_init_req
>> redundant then?
>>
>> https://elixir.bootlin.com/linux/v5.16-rc8/source/drivers/infiniband/sw/rxe/rxe_qp.c#L220
>>
>>
>> Can we remove it?
Based on the discussion with Leon Romanovsky, when in-subnet
communications, GRH is optional.
So It is possible that GRH is not set. Without the randomization for
src_port done in rxe_qp_init_req, udp source
port will be 0xC000 in that case.
So it is better to keep this randomization for src_port done in
rxe_qp_init_req.
Zhu Yanjun
>
> Yes. We can remove it.
> Because this "randomization for src_port done in rxe_qp_init_req" is
> replaced by rdma_get_udp_sport in rxe_modify_qp, I do not remove it.
>
> I will remove it in the latest commits soon.
>
> Zhu Yanjun
>
>>
>>> + qp->src_port = rdma_get_udp_sport(fl, lqp, rqp);
>>> + }
>>> + }
>>> +
>>> return 0;
>>>
>>> err1:
>>> --
>>> 2.27.0
>>
>
prev parent reply other threads:[~2022-01-05 13:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 8:07 [PATCH 0/4] Generate UDP src port with flow label or lqpn/rqpn yanjun.zhu
2022-01-05 8:07 ` [PATCH 1/4] RDMA/core: Calculate UDP source port based on " yanjun.zhu
2022-01-05 13:51 ` Mark Zhang
2022-01-05 14:11 ` Yanjun Zhu
2022-01-05 8:07 ` [PATCH 2/4] RDMA/hns: Replace get_udp_sport with rdma_get_udp_sport yanjun.zhu
2022-01-05 8:07 ` [PATCH 3/4] RDMA/irdma: Make the source udp port vary yanjun.zhu
2022-01-04 17:18 ` Saleem, Shiraz
2022-01-04 19:26 ` Leon Romanovsky
2022-01-05 0:41 ` Yanjun Zhu
2022-01-05 8:07 ` [PATCH 4/4] RDMA/rxe: Use the standard method to produce udp source port yanjun.zhu
2022-01-04 17:17 ` Saleem, Shiraz
2022-01-05 0:33 ` Yanjun Zhu
2022-01-05 13:10 ` Yanjun Zhu [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=8ea540d1-ce89-0248-0bd4-444ca1267e84@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=liangwenpeng@huawei.com \
--cc=linux-rdma@vger.kernel.org \
--cc=liweihang@huawei.com \
--cc=mustafa.ismail@intel.com \
--cc=shiraz.saleem@intel.com \
--cc=zyjzyj2000@gmail.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