| commit | 4ab254017ccda4bc6d94846e1c748ac0f20c0df3 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Fri Nov 06 14:20:21 2015 -0800 |
| committer | Adam Langley <agl@google.com> | Tue Nov 10 19:13:46 2015 +0000 |
| tree | c65a5ac79c257d5d1b54494e04e19f555fcb5057 | |
| parent | ad38dc7452b6bdaf226965b88080736495ac263c [diff] |
Add AArch64 Montgomery assembly. The file armv8-mont.pl is taken from upstream. The speed ups are fairly modest (~30%) but seem worthwhile. Before: Did 231 RSA 2048 signing operations in 1008671us (229.0 ops/sec) Did 11208 RSA 2048 verify operations in 1036997us (10808.1 ops/sec) Did 342 RSA 2048 (3 prime, e=3) signing operations in 1021545us (334.8 ops/sec) Did 32000 RSA 2048 (3 prime, e=3) verify operations in 1016162us (31491.0 ops/sec) Did 45 RSA 4096 signing operations in 1039805us (43.3 ops/sec) Did 3608 RSA 4096 verify operations in 1060283us (3402.9 ops/sec) After: Did 300 RSA 2048 signing operations in 1009772us (297.1 ops/sec) Did 12740 RSA 2048 verify operations in 1075413us (11846.6 ops/sec) Did 408 RSA 2048 (3 prime, e=3) signing operations in 1016139us (401.5 ops/sec) Did 33000 RSA 2048 (3 prime, e=3) verify operations in 1017510us (32432.1 ops/sec) Did 52 RSA 4096 signing operations in 1067678us (48.7 ops/sec) Did 3408 RSA 4096 verify operations in 1062863us (3206.4 ops/sec) Change-Id: Ife74fac784067fce3668b5c87f51d481732ff855 Reviewed-on: https://boringssl-review.googlesource.com/6444 Reviewed-by: David Benjamin <davidben@chromium.org> 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: