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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 14 Dec 2020 10:28:19 +0800 From: Tony W Wang-oc <TonyWWang-oc@...oxin.com> To: Eric Biggers <ebiggers@...nel.org> CC: <herbert@...dor.apana.org.au>, <davem@...emloft.net>, <tglx@...utronix.de>, <mingo@...hat.com>, <bp@...en8.de>, <x86@...nel.org>, <hpa@...or.com>, <linux-crypto@...r.kernel.org>, <linux-kernel@...r.kernel.org>, <TimGuo-oc@...oxin.com>, <CooperYan@...oxin.com>, <QiyuanWang@...oxin.com>, <HerryYang@...oxin.com>, <CobeChen@...oxin.com>, <SilviaZhao@...oxin.com> Subject: Re: [PATCH] crypto: x86/crc32c-intel - Don't match some Zhaoxin CPUs On 12/12/2020 01:43, Eric Biggers wrote: > On Fri, Dec 11, 2020 at 07:29:04PM +0800, Tony W Wang-oc wrote: >> The driver crc32c-intel match CPUs supporting X86_FEATURE_XMM4_2. >> On platforms with Zhaoxin CPUs supporting this X86 feature, When >> crc32c-intel and crc32c-generic are both registered, system will >> use crc32c-intel because its .cra_priority is greater than >> crc32c-generic. This case expect to use crc32c-generic driver for >> some Zhaoxin CPUs to get performance gain, So remove these Zhaoxin >> CPUs support from crc32c-intel. >> >> Signed-off-by: Tony W Wang-oc <TonyWWang-oc@...oxin.com> > > Does this mean that the performance of the crc32c instruction on those CPUs is > actually slower than a regular C implementation? That's very weird. > >From the lmbench3 Create and Delete file test on those chips, I think yes. sincerely Tony
Powered by blists - more mailing lists