| commit | f99c8df09eb5bff426315721bfa5f16a99cad32c | [log] [tgz] |
|---|---|---|
| author | Lynn Boger <laboger@linux.vnet.ibm.com> | Thu Apr 11 15:51:25 2019 -0400 |
| committer | Lynn Boger <laboger@linux.vnet.ibm.com> | Wed Jun 05 12:30:33 2019 +0000 |
| tree | bf6065e606b84170088d78e2dca090666289a8e7 | |
| parent | 20be4c3c3ed52bfccdb2d59a412ee1a936d175a7 [diff] |
poly1305: improve performance with asm for ppc64le
This adds an asm implementation for poly1305 on ppc64le, based on
the amd64 asm implementation using the mac interface.
The improvements on a power8 based on the poly1305 benchmarks are:
name old time/op new time/op delta
64 172ns ± 0% 78ns ± 0% -54.77% (p=1.000 n=1+1)
1K 1.47µs ± 0% 0.59µs ± 0% -59.69% (p=1.000 n=1+1)
2M 2.84ms ± 0% 1.12ms ± 0% -60.47% (p=1.000 n=1+1)
64Unaligned 172ns ± 0% 78ns ± 0% -54.59% (p=1.000 n=1+1)
1KUnaligned 1.47µs ± 0% 0.59µs ± 0% -59.69% (p=1.000 n=1+1)
2MUnaligned 2.84ms ± 0% 1.13ms ± 0% -60.23% (p=1.000 n=1+1)
Write64 100ns ± 0% 46ns ± 0% -53.80% (p=1.000 n=1+1)
Write1K 1.40µs ± 0% 0.56µs ± 0% -59.90% (p=1.000 n=1+1)
Write2M 2.84ms ± 0% 1.12ms ± 0% -60.46% (p=1.000 n=1+1)
Write64Unaligned 100ns ± 0% 46ns ± 0% -53.60% (p=1.000 n=1+1)
Write1KUnaligned 1.40µs ± 0% 0.56µs ± 0% -59.90% (p=1.000 n=1+1)
Write2MUnaligned 2.84ms ± 0% 1.13ms ± 0% -60.22% (p=1.000 n=1+1)
Change-Id: I77cc9bb3645a6b1a6edc414b5651dc37ae4a7410
Reviewed-on: https://go-review.googlesource.com/c/crypto/+/173421
Run-TryBot: Lynn Boger <laboger@linux.vnet.ibm.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Michael Munday <mike.munday@ibm.com>
This repository holds supplementary Go cryptography libraries.
The easiest way to install is to run go get -u golang.org/x/crypto/.... You can also manually git clone the repository to $GOPATH/src/golang.org/x/crypto.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the crypto repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/crypto:” in the subject line, so it is easy to find.
Note that contributions to the cryptography package receive additional scrutiny due to their sensitive nature. Patches may take longer than normal to receive feedback.