On Thu, Dec 03, 2015 at 06:38:20AM -0500, Sowmini Varadhan wrote: > On (12/03/15 09:45), Steffen Klassert wrote: > > pcrypt(echainiv(authenc(hmac(sha1-ssse3),cbc-aes-aesni))) > > > > Result: > > > > iperf -c 10.0.0.12 -t 60 > > ------------------------------------------------------------ > > Client connecting to 10.0.0.12, TCP port 5001 > > TCP window size: 45.0 KByte (default) > > ------------------------------------------------------------ > > [ 3] local 192.168.0.12 port 39380 connected with 10.0.0.12 port 5001 > > [ ID] Interval Transfer Bandwidth > > [ 3] 0.0-60.0 sec 32.8 GBytes 4.70 Gbits/sec > > > > I provide more informatios as soon as the code is available. > > that's pretty good compared to the baseline. > I'd like to try out our patches, when they are ready. > > I think you may get some more improvement if you manually pin the irq > and iperf to specific cpus (at least that was my observation for transp > mode) I do that already. I have dedicated crypto and IO cpus, 2 cpus do networking IO and 4 cpus do crypto (parallelized with pcrypt). The bottleneck is now the cpu that does the TX path (checksumming of the GSO segments). -- 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
