always load aesni or load it when cpu supports it

John-Mark Gurney jmg at funkthat.com
Mon Oct 21 18:36:59 UTC 2013


Poul-Henning Kamp wrote this message on Mon, Oct 21, 2013 at 18:32 +0000:
> In message <20131021182834.GX56872 at funkthat.com>, John-Mark Gurney writes:
> 
> >If you're on a slow system (embeded x86 or arm) that has an AES
> >accelerator, you really want to be using your accelerator than wasting
> >your cpu cycles on large blockes of AES...
> 
> First, as I said in my previous email:  I have still to see "distant"
> crypto accelerator do any good if you have idle CPU, even on a soekris 4801.
					     ^^^^^^^^^

If you don't have idle cpu?  Also, what about power consumption?

> If you have a real-life benchmark showing that, I'd like to see it.
> 
> Second, if you want a limit, at the very least it should be MAXPHYS.

Clearly you didn't completely read my first email, so you're proposing
that we ALWAYS use software AES and never use AES-NI?  At least in the
context of my email, that is what the above statement says...

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."


More information about the freebsd-arch mailing list