diff options
author | Nick Mathewson <nickm@torproject.org> | 2011-11-20 21:43:14 -0500 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2011-11-25 10:32:21 -0500 |
commit | 9814019a54a9a62e27b9e95eec5c9f0e5519fc57 (patch) | |
tree | 6d678cc25c7a04a86c6c9ddaf43a7dde38e387fc /changes | |
parent | 8143074b3f110a41cc83335b70eb19dfe2b749b0 (diff) | |
download | tor-9814019a54a9a62e27b9e95eec5c9f0e5519fc57.tar tor-9814019a54a9a62e27b9e95eec5c9f0e5519fc57.tar.gz |
Use openssl's counter mode implementation when we have 1.0.0 or later
This shaves about 7% off our per-cell AES crypto time for me; the
effect for accelerated AES crypto should be even more, since the AES
calculation itself will make an even smaller portion of the
counter-mode performance.
(We don't want to do this for pre-1.0.0 OpenSSL, since our AES_CTR
implementation was actually faster than OpenSSL's there, by about
10%.)
Fixes issue #4526.
Diffstat (limited to 'changes')
-rw-r--r-- | changes/aes_hackery | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/changes/aes_hackery b/changes/aes_hackery index 82aae238c..b22cefe90 100644 --- a/changes/aes_hackery +++ b/changes/aes_hackery @@ -4,11 +4,13 @@ relatively few servers should still be on any version of OpenSSL that doesn't have good optimized assembly AES. - o Major features: + o Major features (AES performance): - Use OpenSSL's EVP interface for AES encryption, so that all AES operations can use hardware acceleration (if present). Resolves issue #4442. - But only use the EVP interface when AES acceleration is enabled, to avoid a performance regression. Resolves issue #4525. - - + - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode + implementation; it makes AES_CTR about 7% faster than our old one + (which was about 10% faster than the one OpenSSL used to provide). + Resolves issue #4526. |