On 12/01/2015 09:59 AM, Sowmini Varadhan wrote:
But these are all still relatively small things - tweaking them doesnt get me significantly past the 3 Gbps limit. Any suggestions on how to make this budge (or design criticism of the patch) would be welcome.
What do the perf profiles show? Presumably, loss of TSO/GSO means an increase in the per-packet costs, but if the ipsec path significantly increases the per-byte costs...
Short of a perf profile, I suppose one way to probe for per-packet versus per-byte would be to up the MTU. That should reduce the per-packet costs while keeping the per-byte roughly the same.
You could also compare the likes of a single-byte netperf TCP_RR test between ipsec enabled and not to get an idea of the basic path length differences without TSO/GSO/whatnot muddying the waters.
happy benchmarking, rick jones -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
