Stephan Mueller <stephan.muel...@atsec.com> wrote: > for the DRBG and the LRNG work I am doing, I also test the speed of the DRBG. > The DRBG can be considered as a form of block chaining mode on top of a raw > cipher. > > What I am wondering is that when encrypting 256 16 byte blocks, I get a speed > of about 170 MB/s with the AES-NI driver. When using the aes-generic or aes- > asm, I get up to 180 MB/s with all else being equal. Note, that figure > includes a copy_to_user of the generated data.
Why are you using AES? Granted, it is a reasonable idea, but when Ted replaced the non-blocking pool with a DBRG, he used a different cipher (I think chacha, not certain) and I think chose not to use the crypto library implementation to avoid kernel bloat. So he has adopted on of your better ideas. Why not follow his lead on how to implement it? -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
