Skip to content
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

Added XORoshiro-256 PRNG implementation paper and README with detailed behaviour #598

Merged
merged 1 commit into from
Sep 7, 2024

Conversation

Knogle
Copy link
Contributor

@Knogle Knogle commented Sep 6, 2024

Ahoy,

This one i forgot in the first PR, but i consider it to be important, as XORoshiro-256 is a heavily modified and not-yet existing adaption of XORoshiro-128**.

Added detailed documentation for the XORoshiro-256 PRNG implementation, including a comprehensive README and a formal paper outlining the mathematical and statistical analysis in the src/xor folder.

The README explains key differences between XORoshiro-256 and the original XORoshiro-128**, its optimization for nwipe, and usage recommendations. The accompanying paper provides an in-depth exploration of entropy propagation, performance considerations, and empirical test results.

This update formalizes the implementation and supports its use in non-cryptographic applications with high throughput requirements on 64-bit systems.

@PartialVolume PartialVolume merged commit f250aee into martijnvanbrummelen:master Sep 7, 2024
2 checks passed
@Knogle Knogle deleted the poc-xoroshiro branch September 7, 2024 15:30
@Knogle
Copy link
Contributor Author

Knogle commented Sep 12, 2024

Ahoy. I think this one will be the option to go for, in the near future.
As Xoroshiro algorithms can be massively accelerated through FMA instructions (this one isn't yet) I was able to get 4GB/s of throughput. So extremely suitable for massive amount of drives, I will make a PR soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants