On 8/18/20 3:33 PM, Herbert Xu wrote:
On Tue, Aug 18, 2020 at 03:31:10PM -0700, Ben Greear wrote:
I don't think it has been discussed recently, but mac80211 is already
a complicated beast, so if this added any significant complexity
it might not be worth it.
Any bulk data path should be using the async interface, otherwise
performance will seriously suffer should SIMD be unavailable. I
think someone should look at converting wireless to async like IPsec.
Most users in most cases are using hw crypt, so that is likely why
it hasn't gotten a huge amount of effort to optimize the software
crypt path.
If someone wants to give this async api a try for mac80211, I can
test, and I can sponsor the work, but I don't have time to try
to implement it myself.
Thanks,
Ben
Truth is though, I know very little about what changes would be
needed to make it do async decrypt, so maybe it would be a simple
matter?
IPsec was actually quite straightforward.
Cheers,
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
