[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d5dd135b-241f-6116-466d-8505b7e7d697@gmail.com>
Date: Wed, 21 Apr 2021 21:14:37 +0300
From: Sergei Shtylyov <sergei.shtylyov@...il.com>
To: patchwork-bot+netdevbpf@...nel.org,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>
Cc: davem@...emloft.net, kuba@...nel.org, netdev@...r.kernel.org,
linux-renesas-soc@...r.kernel.org
Subject: Re: [PATCH] net: renesas: ravb: Fix a stuck issue when a lot of
frames are received
Hello!
On 4/21/21 9:00 PM, patchwork-bot+netdevbpf@...nel.org wrote:
[...]
>> When a lot of frames were received in the short term, the driver
>> caused a stuck of receiving until a new frame was received. For example,
>> the following command from other device could cause this issue.
>>
>> $ sudo ping -f -l 1000 -c 1000 <this driver's ipaddress>
>>
>> The previous code always cleared the interrupt flag of RX but checks
>> the interrupt flags in ravb_poll(). So, ravb_poll() could not call
>> ravb_rx() in the next time until a new RX frame was received if
>> ravb_rx() returned true. To fix the issue, always calls ravb_rx()
>> regardless the interrupt flags condition.
>>
>> [...]
>
> Here is the summary with links:
> - net: renesas: ravb: Fix a stuck issue when a lot of frames are received
> https://git.kernel.org/netdev/net/c/5718458b092b
>
> You are awesome, thank you!
WTF is this rush?! :-/
I was going to review this patch (it didn't look well to me from th 1s glance)...
[...]
MBR, Sergei
Powered by blists - more mailing lists