always load aesni or load it when cpu supports it

[John-Mark Gurney]

So, I'd like to get aesni more widely used.  I didn't even realize one
of my AMD cpus even supported AES-NI till I decided to look at the caps
and realized it did.  If we had been loading the AES-NI module, I would
have realized it sooner.

So, should we now add it to GENERIC?  or should we (and by we, I mean I)
add code to loader to load it when the cpu supports it?

Yes, the aesni module is small, but dynamicly loading it would allow us
to continue to keep the kernel small, and this could possibly be used as
a framework for other modules too.

Comments?  Suggestions or ideas?

Thanks.

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

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