On Fri, 2014-05-23 at 08:44 -0700, Rick Jones wrote: > If you are measuring performance with the likes of netperf, you should > be able to get an idea of the performance effect from the change in > service demand (CPU consumed per unit of work) even if the maximum > throughput remains capped.
This wont be enough to truly get an idea of the gains this patch brings. Add some random drops in the equation, and instead of dropping packets, we gently add them in the out of order queue, gently coalesce them, gently allow SACK enabled flows to recover thanks to fast retransmits, with no latency effect (No expensive collapse/prunes) # nstat -az|egrep "TCPRcvCoalesce|TCPOFOQueue|TCPRcvCollapsed|Prune" TcpExtPruneCalled 118 0.0 TcpExtRcvPruned 0 0.0 TcpExtOfoPruned 0 0.0 TcpExtTCPRcvCollapsed 1009 0.0 TcpExtTCPRcvCoalesce 857806 0.0 TcpExtTCPOFOQueue 201246 0.0 Yep, we _might_ consume some cpu cycles in the perfect case where no packet was dropped, but this is kind of an utopia. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
