[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0c4902f4-e744-fe95-1a05-51ae936c4516@linux.alibaba.com>
Date: Mon, 7 Feb 2022 15:13:22 +0800
From: "D. Wythe" <alibuda@...ux.alibaba.com>
To: Tony Lu <tonylu@...ux.alibaba.com>
Cc: kgraul@...ux.ibm.com, kuba@...nel.org, davem@...emloft.net,
netdev@...r.kernel.org, linux-s390@...r.kernel.org,
linux-rdma@...r.kernel.org, matthieu.baerts@...sares.net
Subject: Re: [PATCH v2 net-next 3/3] net/smc: Fallback when handshake
workqueue congested
After some trial and thought, I found that the scope of netlink control
is too large, we should limit the scope to socket. Adding a socket
option may be a better choice, what do you think?
在 2022/1/29 下午12:33, Tony Lu 写道:
> On Fri, Jan 28, 2022 at 10:44:38PM +0800, D. Wythe wrote:
>> From: "D. Wythe" <alibuda@...ux.alibaba.com>
>> @@ -19,3 +19,15 @@ config SMC_DIAG
>
> ...
>
>> +if SMC
>> +
>> +config SMC_AUTO_FALLBACK
>> + bool "SMC: automatic fallback to TCP"
>> + default y
>> + help
>> + Allow automatic fallback to TCP accroding to the pressure of SMC-R
>> + handshake process.
>> +
>> + If that's not what you except or unsure, say N.
>> +endif
>
> Using a netlink knob to control behavior with static key should be more
> flexible. As I appended in the previous version of this patch.
>
> Thank you,
> Tony Lu
Powered by blists - more mailing lists