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: Tue, 20 Mar 2012 08:44:57 +0100 From: Steffen Klassert <steffen.klassert@...unet.com> To: Peter Zijlstra <peterz@...radead.org> 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 Sat, Mar 17, 2012 at 10:00:34PM +0100, Peter Zijlstra wrote: > On Fri, 2012-03-16 at 11:44 +0100, Steffen Klassert wrote: > > > > 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. When looking at this, it seems that cpu_online_mask is the mask we should use instead of cpu_active_mask. I'll go in for a closer look at the end of the week. > > > > 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. Indeed, I'll take care for this. -- 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