On Tue, Sep 17, 2013 at 04:33:34PM -0700, Adrian Chadd wrote: > ... I think you should start doing some more in-depth system profiling to > see where that CPU is actually being used. Saying "ksoftirqd" is only a > little helpful. > > See if it's handling way too much interrupts, or whether there's lots of > card error conditions, or the TX/RX queues are being too frequently > checkeed, or ...
>> What I have seen is that with madwifi driver the cpu is 90-100% cpu >> usage with ksoftirqd with mac80211 about 2% ... >> Could this be a kernel interrupt issue? Are there several policies which >> changed with kernel? Indeed I didn't understand at all the stats given above. I took it to mean that madwifi is using much more CPU in the kernel than ath5k, which would be an anti-feature unless ath5k is sleeping too much. At any rate - results of "perf record [do something wireless]" + "perf report" for both scenarios could shed some light. -- Bob Copeland %% www.bobcopeland.com _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
