On Sun, May 07, 2017 at 08:06:56PM -0400, [email protected] wrote: > On 2017-05-07 19:30, Mike Belopuhov wrote: > > You observe a decrease in performance because we've switched to > > a constant time machine independent AES implementation which is > > inherently slower than the T-table version. Users with CPUs > > supporting AES-NI are not affected by this since the AES-NI > > driver provides it's own constant time implementation. > > > > Regards, > > Mike > > Hi Mike, > > Thanks for the info, and for your work on the AES implementation. > With that said, is there any chance that this issue could be solved > such that CPUs like mine (which lack AES-NI) won't become super slow? > > I can always stop using softraid crypto or buy a new CPU, but I'd > like to avoid that :)
I also have some machines which are affected by this, and I am not sure what to about it. I cannot judge the advantages of either AES implementation. If this is how softraid crypto is going to be from now on, I am going to move my non-AES-NI machines off softraid crypto onto self-encrypting SSDs (which is good idea anyway for slow machines).
