Re: [PATCH net-next v5 4/5] net/smc: Dynamic control auto fallback by socket options

D. Wythe
2022-02-09T09:41:40Z

When a large number of connections are influx, the long-connection
service has a much higher tolerance for smc queuing time than the
short-link service. For the long-connection service, more SMC
connections are more important than faster connection establishment, the
auto fallback is quite meaningless and unexpected to them, while the
short-link connection service is in the opposite. When a host has both
types of services below, a global switch cannot works in that case. what
do you think?

Hope for you reply.

Thanks.

在 2022/2/9 下午3:59, Karsten Graul 写道:
> On 09/02/2022 07:41, D. Wythe wrote:
>>
>> Some of our servers have different service types on different ports.
>> A global switch cannot control different service ports individually in this case。In fact, it has nothing to do with using netlink or not. Socket options is the first solution comes to my mind in that case，I don't know if there is any other better way。
>>
>
> I try to understand why you think it is needed to handle different
> service types differently. As you wrote
>
>> After some trial and thought, I found that the scope of netlink control is too large
>
> please explain what you found out. I don't doubt about netlink or socket option here,
> its all about why a global switch for this behavior isn't good enough.