On Wed, Jul 13, 2016 at 10:53 AM, Felix Fietkau <nbd@xxxxxxxx> wrote: >> To me this implies a contending lock issue, too much work in the irq >> handler or too delayed work in the softirq handler.... >> >> I thought you were very brave to try and backport this. > I don't think this has anything to do with contending locks, CPU > utilization, etc. The code does something to the packets that TCP really > doesn't like. With your 70% idle figure, I am inclined to agree... could you get an aircap of the two different tests? - as well as a regular packetcap taken at the client or server? And put somewhere I can get at them? What version of OSX are you running? I will setup an ath9k box shortly... -- Dave Täht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org -- 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
