On Sun, 2009-04-19 at 19:11 -0400, Chris Mason wrote:
> How does this enable the HW crc32c? Unless I'm missing something you're
> doing crc32c instead of btrfs_crc32c, but btrfs_crc32c was #defined to
> crc32c?
It doesn't. You're _already_ using the hardware crc32c.
Since commit 69c35efc, all users of crc32c() in libcrc32c are actually
using the cryptoapi and thus any accelerated hardware implementations
that are available:
libcrc32c: Move implementation to crypto crc32c
This patch swaps the role of libcrc32c and crc32c. Previously
the implementation was in libcrc32c and crc32c was a wrapper.
Now the code is in crc32c and libcrc32c just calls the crypto
layer.
The reason for the change is to tap into the algorithm selection
capability of the crypto API so that optimised implementations
such as the one utilising Intel's CRC32C instruction can be
used where available.
Signed-off-by: Herbert Xu <herb...@gondor.apana.org.au>
--
David Woodhouse Open Source Technology Centre
david.woodho...@intel.com Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
