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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 31 May 2012 08:34:02 +1000
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Johannes Goetzfried 
	<Johannes.Goetzfried@...ormatik.stud.uni-erlangen.de>,
	Jussi Kivilinna <jussi.kivilinna@...et.fi>,
	linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org,
	Tilo Müller 
	<Tilo.Mueller@...ormatik.uni-erlangen.de>
Subject: Re: [PATCH] crypto: serpent - add x86_64/avx assembler
 implementation

On Wed, May 30, 2012 at 11:55:37PM +0200, Andi Kleen wrote:
> On Thu, May 31, 2012 at 07:44:48AM +1000, Herbert Xu wrote:
> > On Wed, May 30, 2012 at 11:40:06PM +0200, Andi Kleen wrote:
> > >
> > > > What we could do is to use the cpuid-based probing when an algorithm
> > > > is needed to selectively load the relevant implementations instead
> > > > of all of them.  However, for most algorithms it won't make that
> > > > big a difference since all the available ones will be loaded anyway.
> > > 
> > > Yes cpuid probing does that.
> > 
> > I was under the impression that using cpuid meant that the algorithm
> > would be loaded regardless of whether it has been requested, as long
> > as the cpuid matches.
> 
> It loads it always correct.

You mean with cpuid it'll always load the algorithm if it is
available even if noone is using it? Then it's probably not a
good fit for serpent.

Cheers,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ