Re: [OpenWrt-Devel] [PATCH] ramips: ethernet: fix to interrupt handling

2019-10-31 Thread Mingyu Li
the upstream kernel. the function mtk_napi_rx always be called if it have packet to receive. it doesn't check status register. but on openwrt code. check the status register first. then call fe_poll_rx. if you clear status register. fe_poll_rx will will not be called next time. Rosen Penev 於

Re: [OpenWrt-Devel] [PATCH] ramips: ethernet: fix to interrupt handling

2019-10-29 Thread Rosen Penev
On Wed, Mar 6, 2019 at 12:37 AM Mingyu Li wrote: > > the original code use status register to keep there still have some > pkts in buffer. > need next napi call to receive it. > > if 128 packets in buffer. you clear status first. because napi max > handle 64 packets in buffer. > so 64 packets

Re: [OpenWrt-Devel] [PATCH] ramips: ethernet: fix to interrupt handling

2019-03-06 Thread Mingyu Li
the original code use status register to keep there still have some pkts in buffer. need next napi call to receive it. if 128 packets in buffer. you clear status first. because napi max handle 64 packets in buffer. so 64 packets need to handle in next napi poll. if no new packet comming. the

[OpenWrt-Devel] [PATCH] ramips: ethernet: fix to interrupt handling

2019-03-05 Thread Rosen Penev
From: NeilBrown The current code acknowledged interrupts *after* polling. This is the wrong way around, and could cause an interrupt to be missed. This is not likely to be fatal as another packet, and so another interrupt, should come along soon. But maybe it is causing problems, so let's fix