Message ID | 20250130035130.180676-1-ebiggers@kernel.org (mailing list archive) |
---|---|
Headers | show |
Series | CRC64 library rework and x86 CRC optimization | expand |
On Wed, Jan 29, 2025 at 07:51:19PM -0800, Eric Biggers wrote: > Patch 11 wires up the same optimization to crc64_be() and crc64_nvme() > (a.k.a. the old "crc64_rocksoft") which previously were unoptimized, Yes, I mistakenly thought the name of the table in the spec was the name of the CRC, but that was just referring to format of how the parameters were displayed. It really should have been crc64_nvme, so thank you for clearing up the naming confusion. > improving the performance of those CRC functions by as much as 100x. Awesome! Looks good: Acked-by: Keith Busch <kbusch@kernel.org>
Eric, > Patches 1-5 rework the CRC64 library along the lines of what I did for > CRC32 and CRC-T10DIF in 6.14. They add direct support for > architecture-specific optimizations, fix the naming of the NVME CRC64 > variant, and eliminate a pointless use of the crypto API. > > Patches 6-10 replace the existing x86 PCLMULQDQ optimized CRC code > with new code that is shared among the different CRC variants and also > adds VPCLMULQDQ support, greatly improving performance on recent CPUs. > Patch 11 wires up the same optimization to crc64_be() and crc64_nvme() > (a.k.a. the old "crc64_rocksoft") which previously were unoptimized, > improving the performance of those CRC functions by as much as 100x. > crc64_be is used by bcachefs, and crc64_nvme is used by blk-integrity. Very nice! Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>