On Thu, 14 Sept 2023 at 10:28, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote: > > This series introduces the lskcipher API type. Its relationship > to skcipher is the same as that between shash and ahash. > > This series only converts ecb and cbc to the new algorithm type. > Once all templates have been moved over, we can then convert the > cipher implementations such as aes-generic. > > Ard, if you have some spare cycles you can help with either the > templates or the cipher algorithm conversions. The latter will > be applied once the templates have been completely moved over. > > Just let me know which ones you'd like to do so I won't touch > them. > Hello Herbert, Thanks for sending this. So the intent is for lskcipher to ultimately supplant the current cipher entirely, right? And lskcipher can be used directly by clients of the crypto API, in which case kernel VAs may be used directly, but no async support is available, while skcipher API clients will gain access to lskciphers via a generic wrapper (if needed?) That makes sense but it would help to spell this out. I'd be happy to help out here but I'll be off on vacation for ~3 weeks after this week so i won't get around to it before mid October. What I will do (if it helps) is rebase my recent RISC-V scalar AES cipher patches onto this, and implement ecb(aes) instead (which is the idea IIUC?)
