On Sun, Jul 24, 2011 at 07:53:14PM +0200, Mathias Krause wrote: > > With this algorithm I was able to increase the throughput of a single > IPsec link from 344 Mbit/s to 464 Mbit/s on a Core 2 Quad CPU using > the SSSE3 variant -- a speedup of +34.8%. Were you testing this on the transmit side or the receive side? As the IPsec receive code path usually runs in a softirq context, does this code have any effect there at all? This is pretty similar to the situation with the Intel AES code. Over there they solved it by using the asynchronous interface and deferring the processing to a work queue. This also avoids the situation where you have an FPU/SSE using process that also tries to transmit over IPsec thrashing the FPU state. Now I'm still happy to take this because hashing is very different from ciphers in that some users tend to hash small amounts of data all the time. Those users will typically use the shash interface that you provide here. So I'm interested to know how much of an improvement this is for those users (< 64 bytes). If you run the tcrypt speed tests that should provide some useful info. Thanks, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- 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
