[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <d2195919-1cae-b667-c137-8398848fa43b@linux.alibaba.com>
Date: Thu, 30 Jun 2022 22:29:53 +0800
From: Guangguan Wang <guangguan.wang@...ux.alibaba.com>
To: Wenjia Zhang <wenjia@...ux.ibm.com>
Cc: davem@...emloft.net, Karsten Graul <kgraul@...ux.ibm.com>,
liuyacan@...p.netease.com, kuba@...nel.org,
linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
netdev@...r.kernel.org, pabeni@...hat.com
Subject: Re: [PATCH net-next v2] net/smc: align the connect behaviour with TCP
On 2022/6/30 04:09, Wenjia Zhang wrote:
>
> Since Karsten's suggestion, we didn't hear from you any more. We just want to know:
>
> - What do you think about the commit (86434744)? Could it be the trigger of the problem you met?
>
> - Have you ever tried to just remove the following lines from smc_connection(), and check if your scenario could run correctly?
>
> if (smc->use_fallback)
> goto out;
>
> In our opinion, we don't see the necessity of the patch, if partly reverting the commit (86434744) could solve the problem.
I'm so sorry I missed the last emails for this discussion.
Yes, commit (86434744) is the trigger of the problem described in
https://lore.kernel.org/linux-s390/45a19f8b-1b64-3459-c28c-aebab4fd8f1e@linux.alibaba.com/#t .
And I have tested just remove the following lines from smc_connection() can solve the above problem.
if (smc->use_fallback)
goto out;
I aggree that partly reverting the commit (86434744) is a better solution.
Thanks,
Guangguan Wang
Powered by blists - more mailing lists