Support for CRC-64/NVME - the default AWS S3 checksum algorithm
#386
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The default checksum algorithm for new uploaded objects to AWS S3 is
CRC-64/NVME, according to their documentation: https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.htmlThe description and references below were taken from https://github.com/awesomized/crc64fast-nvme:
CRC-64/NVME comes from the NVM Express® NVM Command Set Specification (Revision 1.0d, December 2023) and has also been implemented in the Linux kernel (where it's called CRC-64/Rocksoft) and is AWS S3's recommended checksum option as CRC64-NVME. (Note that the Check value in the spec uses incorrect endianness [Section 5.2.1.3.4, Figure 120, page 83]).
Other references: