| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 04 Aug 2008 06:58:01 -0400 From: Austin Zhang <austin_zhang@...ux.intel.com> To: David Woodhouse <dwmw2@...radead.org> Cc: herbert@...dor.apana.org.au, davem@...emloft.net, linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org Subject: Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API. On Mon, 2008-08-04 at 11:45 +0100, David Woodhouse wrote: > Are we deprecating libcrc32c, then? Or just turning it into a wrapper > around the crypto code? Maybe I can pick up crc32c_intel_le_hw_byte and crc32c_intel_le_hw into one arch-related file and make the current new crypto interface and libcrc32c call it. > Either way, does it really make sense to force all crc32 users to pull > in the whole crypto framework? Some may get fractious about that... If there were really few (or no) user using that previous interface, it will be reasonable to merge the crc32c totally into crypto subsystem as a digest method. And I remembered Herbert had mentioned he will convert those previous interface calling to new crypto API. For the crc32c, he had done for it. BTW, why did I always got each email on this thread twice:(? (the same email twice) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists