From: "D. Wythe" <alibuda@linux.alibaba.com>
To: Karsten Graul <kgraul@linux.ibm.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
Tony Lu <tonylu@linux.alibaba.com>
Subject: Re: [PATCH net-next v4 3/3] net/smc: Fallback when handshake workqueue congested
Date: Mon, 7 Feb 2022 17:50:44 +0800 [thread overview]
Message-ID: <f1ed4d54-d658-c668-99af-9994a634baf3@linux.alibaba.com> (raw)
In-Reply-To: <bab2d7f1-c57a-cab4-3963-23721292eece@linux.ibm.com>
The main communication in v2 series is about adding a dynamic control
for auto fallback to TCP. I will soon add a new patch to implements this
in v5 series, or modify it in curret patch. Which one do you recommend?
Look forward to your suggestions.
Thanks.
在 2022/2/7 下午3:56, Karsten Graul 写道:
> On 07/02/2022 07:24, D. Wythe wrote:
>> From: "D. Wythe" <alibuda@linux.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.
>
> I hope I didn't miss any news, but with your latest reply to the v2 series you
> questioned the config option in this v4 patch, so this is still work in progress, right?
next prev parent reply other threads:[~2022-02-07 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 6:24 [PATCH net-next v4 0/3] net/smc: Optimizing performance in short-lived scenarios D. Wythe
2022-02-07 6:24 ` [PATCH net-next v4 1/3] net/smc: Make smc_tcp_listen_work() independent D. Wythe
2022-02-07 6:24 ` [PATCH net-next v4 2/3] net/smc: Limits backlog connections D. Wythe
2022-02-07 6:24 ` [PATCH net-next v4 3/3] net/smc: Fallback when handshake workqueue congested D. Wythe
2022-02-07 7:56 ` Karsten Graul
2022-02-07 9:50 ` D. Wythe [this message]
2022-02-07 10:03 ` Karsten Graul
2022-02-08 12:58 ` D. Wythe
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=f1ed4d54-d658-c668-99af-9994a634baf3@linux.alibaba.com \
--to=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tonylu@linux.alibaba.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