| commit | 99767ecdd437ddff3352e90a019d8df7e4b816ea | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu May 03 16:38:08 2018 -0400 |
| committer | Adam Langley <agl@google.com> | Fri May 11 21:57:13 2018 +0000 |
| tree | ecc646e42f65db9c50a2c317af7a6795402ccd49 | |
| parent | b06f92da7be85387d037bea40e5b9de5e94ef180 [diff] |
Enable ADX assembly. Build (and carry) issues are now resolved (as far as we know). Let's try this again... Measurements on a Skylake VM (so a little noisy). Before: Did 3135 RSA 2048 signing operations in 3015866us (1039.5 ops/sec) Did 89000 RSA 2048 verify (same key) operations in 3007271us (29594.9 ops/sec) Did 66000 RSA 2048 verify (fresh key) operations in 3014363us (21895.2 ops/sec) Did 324 RSA 4096 signing operations in 3004364us (107.8 ops/sec) Did 23126 RSA 4096 verify (same key) operations in 3003398us (7699.9 ops/sec) Did 21312 RSA 4096 verify (fresh key) operations in 3017043us (7063.9 ops/sec) Did 31040 ECDH P-256 operations in 3024273us (10263.6 ops/sec) Did 91000 ECDSA P-256 signing operations in 3019740us (30135.0 ops/sec) Did 25678 ECDSA P-256 verify operations in 3046975us (8427.4 ops/sec) After: Did 3640 RSA 2048 signing operations in 3035845us (1199.0 ops/sec) Did 129000 RSA 2048 verify (same key) operations in 3003691us (42947.2 ops/sec) Did 105000 RSA 2048 verify (fresh key) operations in 3029935us (34654.2 ops/sec) Did 510 RSA 4096 signing operations in 3014096us (169.2 ops/sec) Did 38000 RSA 4096 verify (same key) operations in 3092814us (12286.5 ops/sec) Did 34221 RSA 4096 verify (fresh key) operations in 3003817us (11392.5 ops/sec) Did 38000 ECDH P-256 operations in 3061758us (12411.2 ops/sec) Did 116000 ECDSA P-256 signing operations in 3001637us (38645.6 ops/sec) Did 35100 ECDSA P-256 verify operations in 3023872us (11607.6 ops/sec) Tested with Intel SDE. Change-Id: Ib27c0d6012d14274e331ab03f958e5a0c8b7e885 Reviewed-on: https://boringssl-review.googlesource.com/28104 Reviewed-by: Adam Langley <agl@google.com>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
There are other files in this directory which might be helpful: