-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support SHA* intrinsics on Intel CPU #37
Conversation
- optimise: select block function at init - added dedicated padding function, optimised endian conversion - add assembly for Intel SHA extensions - update benchmarks - stream line checksum function - cleanup of sha assembly code
49980ad
to
771b9fb
Compare
771b9fb
to
3912658
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after review
Any idea on performance gains? |
Not yet we are still looking for a CPU to test.. |
On my Ryzen 7 with syncthings benchmark.
After:
|
Oh wow thanks - would you be interested in submitting the |
Gimme a sec |
|
Thanks looks quite promising. |
@AudriusButkevicius can you provide the cpuinfo for your processor would like to add this under https://github.com/minio/sha256-simd#performance
|
@harshavardhana @fwessels The code in this PR #37 (which was merged) appears to be my work with minor changes. While I am happy to license this code to your project under the Apache 2.0 open source license, I must insist on proper attribution and identication of copyright holders. In particular, the assembly language source file sha256blockSha_amd64.s is my original work and I hold copyright in it. Please kindly correct the copyright notice that you have added to this file accordingly. Please contact me directly on Gitter to discuss further. |
@svenski123 let me know what is the copyright it can be definitely added. |
These days, a more realistic number of guesses per second per CPU is 10,000, corresponding e.g. to 5,000 round SHA-256 (e.g. Linux/glibc crypt) using dedicated CPU SHA-256 instructions.[1] Also, studies are not clear on the benefits of passphrases with regard to retention.[2] [1]: minio/sha256-simd#37 (comment) [2]: https://cups.cs.cmu.edu/soups/2012/proceedings/a7_Shay.pdf
No description provided.