[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bb84bb0a-7b9d-12c6-86a3-8e5c4eea1ba6@linux.alibaba.com>
Date: Wed, 3 Nov 2021 16:56:19 +0800
From: Wen Gu <guwen@...ux.alibaba.com>
To: Karsten Graul <kgraul@...ux.ibm.com>,
Tony Lu <tonylu@...ux.alibaba.com>, davem@...emloft.net,
kuba@...nel.org
Cc: netdev@...r.kernel.org, linux-s390@...r.kernel.org,
linux-rdma@...r.kernel.org, jacob.qi@...ux.alibaba.com,
xuanzhuo@...ux.alibaba.com, dust.li@...ux.alibaba.com,
guwen@...ux.alibaba.com
Subject: Re: [PATCH net 4/4] net/smc: Fix wq mismatch issue caused by smc
fallback
On 2021/11/2 下午5:25, Karsten Graul wrote:
> On 01/11/2021 07:15, Wen Gu wrote:
>> Before explaining my intentions, I thought it would be better to describe the issue I encountered first:
>>
>> In nginx/wrk tests, when nginx uses TCP and wrk uses SMC to replace TCP, wrk should fall back to TCP and get correct results theoretically, But in fact it only got all zeros.
>
> Thank you for the very detailed description, I now understand the situation.
>
> The fix is not obvious and not easy to understand for the reader of the code,
> did you think about a fix that uses own sk_data_ready / sk_write_space
> implementations on the SMC socket to forward the call to the clcsock in the
> fallback situation?
>
> I.e. we already have smc_tx_write_space(), and there is smc_clcsock_data_ready()
> which is right now only used for the listening socket case.
>
> If this works this would be a much cleaner and more understandable way to fix this issue.
>
Thanks for your suggestions, they are very helpful.
I will try these ways and send a new patch later.
cheers,
Wen Gu
Powered by blists - more mailing lists