linux-kernel - Re: cpu_active vs pcrypt & padata

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:	Fri, 16 Mar 2012 11:20:15 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	David Miller <davem@...emloft.net>
Cc:	steffen.klassert@...unet.com, mingo@...e.hu, tglx@...utronix.de,
	linux-kernel@...r.kernel.org
Subject: Re: cpu_active vs pcrypt & padata

On Fri, 2012-03-16 at 03:16 -0700, David Miller wrote:
> From: Peter Zijlstra <peterz@...radead.org>
> Date: Fri, 16 Mar 2012 11:13:08 +0100
> 
> > Also, wth is all this kernel/padata.c stuff? There's next to no useful
> > comment in there and the only consumer seems to be pcrypt, does that
> > really need to be in kernel/ ?
> 
> There's really nothing specific to crypto in that padata.c file,
> anything trying to compute things in parallel with some kind
> of converging synchronization points can use that code.

So why isn't anybody else using that? Don't the block/fs people need
similar things?
--
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/