From: Chao Leng <lengchao@huawei.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: <leon@kernel.org>, <linux-rdma@vger.kernel.org>
Subject: Re: [for-next PATCH] infiniband:cma: add a parameter for the packet lifetime
Date: Thu, 24 Nov 2022 16:19:35 +0800 [thread overview]
Message-ID: <c581c96c-b9a4-d5e8-a8ba-d8fce93fe32d@huawei.com> (raw)
In-Reply-To: <Y355I/a/62kl0e07@nvidia.com>
On 2022/11/24 3:48, Jason Gunthorpe wrote:
> On Wed, Nov 23, 2022 at 10:13:48AM +0800, Chao Leng wrote:
>>
>>
>> On 2022/11/22 22:08, Jason Gunthorpe wrote:
>>> On Tue, Nov 22, 2022 at 05:02:06PM +0800, Chao Leng wrote:
>>>> Now the default packet lifetime(CMA_IBOE_PACKET_LIFETIME) is 18.
>>>> That means the minimum ack timeout is 2 seconds(2^(18+1)*4us=2.097seconds).
>>>> The packet lifetime means the maximum transmission time of packets
>>>> on the network, the maximum transmission time of packets is closely
>>>> related to the network. 2 seconds is too long for simple lossless networks.
>>>> The packet lifetime should allow the user to adjust according to the
>>>> network situation.
>>>> So add a parameter for the packet lifetime.
>>>>
>>>> Signed-off-by: Chao Leng <lengchao@huawei.com>
>>>> ---
>>>> drivers/infiniband/core/cma.c | 6 +++++-
>>>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/infiniband/core/cma.c b/drivers/infiniband/core/cma.c
>>>> index cc2222b85c88..8e2ff5d610e3 100644
>>>> --- a/drivers/infiniband/core/cma.c
>>>> +++ b/drivers/infiniband/core/cma.c
>>>> @@ -50,6 +50,10 @@ MODULE_LICENSE("Dual BSD/GPL");
>>>> #define CMA_IBOE_PACKET_LIFETIME 18
>>>> #define CMA_PREFERRED_ROCE_GID_TYPE IB_GID_TYPE_ROCE_UDP_ENCAP
>>>> +static unsigned char cma_packet_lifetime = CMA_IBOE_PACKET_LIFETIME;
>>>> +module_param_named(packet_lifetime, cma_packet_lifetime, byte, 0644);
>>>> +MODULE_PARM_DESC(packet_lifetime, "max transmission time of the packet");
>>>
>>> No new module parameters
>>>
>>> Maybe something in netlink would be appropriate, I'm not sure how
>>> best to deal with this.
>>>
>>> Really, the entire retransmit strategy in CM is not suitable for
>>> ethernet networks, this is just one symptom.
>> What do you think to change the CMA_IBOE_PACKET_LIFETIME to 16.
>> The maximum transmission time of packets will be about 500+ms,
>> I think this is long enough for RoCE networks.
>> 2 seconds is too long to my honest.
>
> I don't have an informed opinion on this. I agree that 2s is too long though
>
> Do we have any information to back up what this should be?
Assume the network is a clos topology with three layers, every packet
will pass through five hops of switches. Assume the buffer of every
switch is 128MB and the port transmission rate is 25 Gbit/s,
the maximum transmission time of the packet is 200ms(128MB*5/25Gbit/s).
Add double redundancy, it is less than 500ms.
So change the CMA_IBOE_PACKET_LIFETIME to 16,
the maximum transmission time of the packet will be about 500+ms,
it is long enough.
next prev parent reply other threads:[~2022-11-24 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 9:02 [for-next PATCH] infiniband:cma: add a parameter for the packet lifetime Chao Leng
2022-11-22 14:08 ` Jason Gunthorpe
2022-11-23 2:13 ` Chao Leng
2022-11-23 19:48 ` Jason Gunthorpe
2022-11-24 8:19 ` Chao Leng [this message]
2022-11-24 13:22 ` Jason Gunthorpe
2022-11-25 0:43 ` Chao Leng
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=c581c96c-b9a4-d5e8-a8ba-d8fce93fe32d@huawei.com \
--to=lengchao@huawei.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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