always load aesni or load it when cpu supports it

[Poul-Henning Kamp]

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 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.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.