Closed vkrasnov closed 6 months ago
Attention: 1 lines
in your changes are missing coverage. Please review.
Comparison is base (
c1e31b8
) 96.22% compared to head (5ac1d08
) 96.23%.
Files | Patch % | Lines |
---|---|---|
src/aead/gcm.rs | 75.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
I have now tested this on Windows 11 aarch64-pc-windows-msvc and verified that the implementation is selected and that the tests pass.
And how the performance on that platform?
And how the performance on that platform?
I didn't run the benchmarks because I actually ran the test in Parallels on an M1 Mac. The only ARM64 Windows hardware I have is an original Surface Pro X (SQ1) tablet which isn't very relevant.
Currently ring bundles an interleaved AES-GCM implementation for aarch64, but does not make use of it, instead calling AES-CTR + GHASH in succession.
This change makes use of the bundled implementation, resulting in speedups of 45% for AES-128-GCM and 55% for AES-256-GCM on Apple M1 CPU.