From: Sowmini Varadhan > Sent: 01 December 2015 18:37 ... > I was using esp-null merely to not have the crypto itself perturb > the numbers (i.e., just focus on the s/w overhead for now), but here > are the numbers for the stock linux kernel stack > Gbps peak cpu util > esp-null 1.8 71% > aes-gcm-c-256 1.6 79% > aes-ccm-a-128 0.7 96% > > That trend made me think that if we can get esp-null to be as close > as possible to GSO/GRO, the rest will follow closely behind. That's not how I read those figures. They imply to me that there is a massive cost for the actual encryption (particularly for aes-ccm-a-128) - so whatever you do to the esp-null case won't help. One way to get a view of the cost of the encryption (and copies) is to do the operation twice. David -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
