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: Sat, 17 Mar 2012 22:00:34 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Steffen Klassert <steffen.klassert@...unet.com> Cc: Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: cpu_active vs pcrypt & padata On Fri, 2012-03-16 at 11:44 +0100, Steffen Klassert wrote: > Hi. > > On Fri, Mar 16, 2012 at 11:13:08AM +0100, Peter Zijlstra wrote: > > Hi Steffen, > > > > I found cpu_active usage in crypto/pcrypt.c and was wondering what > > that's doing there. I would really like to contain that thing to as > > narrow a piece of kernel as I possible can (sched/cpuset/hotplug) but it > > appears to be spreading. > > pcrypt uses cpu_active to tell padata which cpuset it whishes > to use for parallelization. I could try to push the cpumask > handling down to padata if you want to limit this to the core > kernel. /me more confused now.. cpu_active isn't in any way shape or form related to cpusets. > > 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/ ? > > The padata code is generic and not limited to crypto, you can find > a documentation at Documentation/padata.txt. Would be nice to have a short blurb in kernel/padata.c with a reference to that Documentation stuff for more in-depth bits. -- 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