On Fri, Nov 05, 2021 at 01:59:35PM +0000, Dmitry Safonov wrote: > On 11/5/21 09:54, Leonard Crestez wrote: > > > This pool pattern is a workaround for crypto-api only being able to > > allocate transforms from user context. > >> It would be useful for this "one-transform-per-cpu" object to be part of > > crypto api itself, there is nothing TCP-specific here other than the > > size of scratch buffer. > > Agree, it would be nice to have something like this as a part of crypto. > The intention here is to reuse md5 sig pool, rather than introduce > another similar one. As I said before, I'm happy to see the ahash/shash interface modified so that we allow the key to be in the request object in addition to the tfm. However, I don't really have the time to work on that and nobody else from the crypto side seems interested in this. So if you guys have the time and are willing to work on it then I'm more than happy to help you. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
