aboutsummaryrefslogtreecommitdiffstats
path: root/package/libs/ocf-crypto-headers
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@openwrt.org>2014-02-27 23:02:37 +0000
committerFelix Fietkau <nbd@openwrt.org>2014-02-27 23:02:37 +0000
commit96eb3d883dde86b8af2748d5932d5c53a35dbb8c (patch)
tree7f9d21212d66ef9ea9db5e03a1c5fe68d0af9608 /package/libs/ocf-crypto-headers
parentf7f117b88df3728c116902c29b04b59b38600633 (diff)
downloadupstream-96eb3d883dde86b8af2748d5932d5c53a35dbb8c.tar.gz
upstream-96eb3d883dde86b8af2748d5932d5c53a35dbb8c.tar.bz2
upstream-96eb3d883dde86b8af2748d5932d5c53a35dbb8c.zip
cns3xxx: ethernet - resolve SMP issue
The combination of r35942 and r35952 causes an issue where eth_schedule_poll() can be called from a different CPU between the call to napi_complete() and the setting of cur_index which can break the rx ring accounting and cause ethernet latency and/or ethernet stalls. The issue can be easilly created by adding a couple of artificial delays such as: @@ -715,6 +715,7 @@ static int eth_poll(struct napi_struct *napi, int budget) if (!received) { napi_complete(napi); +udelay(1000); enable_irq(IRQ_CNS3XXX_SW_R0RXC); } @@ -727,6 +728,7 @@ static int eth_poll(struct napi_struct *napi, int budget) rx_ring->cur_index = i; wmb(); +udelay(1000); enable_rx_dma(sw); return received; This patch moves the setting of cur_index back up where it needs to be and addresses the original corner case that r35942 was trying to catch in an improved fashion by checking to see if the rx descriptor ring has become full before interrupts were re-enabled so that a poll can be scheduled again and avoid an rx stall caused by rx interrupts ceasing to fire again. Signed-off-by: Tim Harvey <tharvey@gateworks.com> SVN-Revision: 39761
Diffstat (limited to 'package/libs/ocf-crypto-headers')
0 files changed, 0 insertions, 0 deletions