[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1825f5e8-6d13-a317-4a96-f4a4fcf07409@tessares.net>
Date: Thu, 27 Jan 2022 18:09:20 +0100
From: Matthieu Baerts <matthieu.baerts@...sares.net>
To: "D. Wythe" <alibuda@...ux.alibaba.com>, kgraul@...ux.ibm.com
Cc: kuba@...nel.org, davem@...emloft.net, netdev@...r.kernel.org,
linux-s390@...r.kernel.org, linux-rdma@...r.kernel.org,
MPTCP Upstream <mptcp@...ts.linux.dev>
Subject: Re: [PATCH net-next 3/3] net/smc: Fallback when handshake workqueue
congested
Hi,
(+cc MPTCP ML)
On 27/01/2022 13:08, D. Wythe wrote:
> From: "D. Wythe" <alibuda@...ux.alibaba.com>
>
> This patch intends to provide a mechanism to allow automatic fallback to
> TCP according to the pressure of SMC handshake process. At present,
> frequent visits will cause the incoming connections to be backlogged in
> SMC handshake queue, raise the connections established time. Which is
> quite unacceptable for those applications who base on short lived
> connections.
(...)
> diff --git a/net/smc/Kconfig b/net/smc/Kconfig
> index 1ab3c5a..1903927 100644
> --- a/net/smc/Kconfig
> +++ b/net/smc/Kconfig
> @@ -19,3 +19,15 @@ config SMC_DIAG
> smcss.
>
> if unsure, say Y.
> +
> +if MPTCP
After having read the code and the commit message, it is not clear to me
why this new feature requires to have MPTCP enabled. May you share some
explanations about that please?
> +
> +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
Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
Powered by blists - more mailing lists