On 21 April 2014 16:14, Tim Harvey <tharvey@xxxxxxxxxxxxx> wrote: > Implement a recv budget so that in cases of high traffic we still allow other > taskets to get processed. > > Without this, we can encounter a host of issues during high wireless traffic > reception depending on system load including rcu stall's detected (ARM), > soft lockups, failure to service critical tasks such as watchdog resets, > and triggering of the tx stuck tasklet. Are you also force rescheduling the Rx tasklet if you break? You can definitely hit a race condition where you get RXEOL and RXDESC before you run the scheduled RX tasklet. In that instance you may not get any further interrupts until you re-poke the RX DMA engine. Adding a FIFO entry may be enough, but it certainly isn't enough (ie, no FIFOs) on pre-AR93xx chips. (I've done the same thing in FreeBSD for the same reasons. It's .. delicate to get right.) -a -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
