On Wed, 11 Mar 2015, Felix Fietkau wrote:
On 2015-03-10 20:22, Zefir Kurtisi wrote:
On 03/09/2015 11:28 PM, David Lang wrote:
On Mon, 9 Mar 2015, José Vázquez wrote:
This gives at least two sources for optimization for the reference driver: 1)
save
inter-layer processing overhead (passing commands from hostapd directly to HW is
cheaper than passing it through 4 layers), and 2) vastly reduce locking when you
are in full control of concurrency.
The overhead of commands issued by hostapd is pretty much irrelevant.
All that matters for driver performance is the actual data path (network
stack, mac80211 tx/rx, driver tx/rx).
Also, I've not seen any indication in my tests that locking is a
measurable cause of performance issues.
When it comes to performance issues, guesswork is meaningless,
measurements (e.g. profiling results) matter!
netperf-wrapper (https://github.com/tohojo/netperf-wrapper) defines a number of
tests that we have found extremely useful in measuring bufferbloat (bad latency
increases while large transfers are taking place), These tests show
upload/download speeds as well as latency measurements.
David Lang
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
