[tor-talk] Tor and AES-NI acceleration , and Tor profiling

[Watson Ladd]

So why doesn't aes.c use the same thing as is initialized in crypto.c?
It would seem that this is always the right thing to do, and that
because we don't do it acceleration only works for some uses of AES.
The fix seems to be to change aes.c's use of defines to match that in
crypto.c.
Sincerely,
Watson Ladd

On Sat, Nov 19, 2011 at 11:35 PM, Nick Mathewson <nickm at torproject.org> wrote:
> On Tue, Nov 8, 2011 at 10:29 AM, Nick Mathewson <nickm at torproject.org> wrote:
>> Hmm.  On examination it looks like there might be some uses of
>> OpenSSL's AES_encrypt function left around in your profile.  Try
>> changing the beginning of Tor's aes.c so that the line that now says:
>>
>>  #undef USE_OPENSSL_EVP
>>
>> now says
>>
>>  #define USE_OPENSSL_EVP
>>
>> Does that improve matters at all?
>
> Curious whether you had a chance to try this.  From   the latest
> profile, your biggest timesink is _x86_64_AES_encrypt_compact.  But
> that's not the AESNI version.  I think that using EVP there would get
> the right result, if I understand how engines work correctly.
>
> --
> Nick
> _______________________________________________
> tor-talk mailing list
> tor-talk at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>



-- 
"Those who would give up Essential Liberty to purchase a little
Temporary Safety deserve neither  Liberty nor Safety."
-- Benjamin Franklin