| 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
| ||
|
Date: Tue, 31 Mar 2009 13:20:42 -0400 (EDT) From: Christoph Lameter <cl@...ux.com> To: Martin Schwidefsky <schwidefsky@...ibm.com> cc: Tejun Heo <tj@...nel.org>, Ingo Molnar <mingo@...e.hu>, rusty@...tcorp.com.au, tglx@...utronix.de, x86@...nel.org, linux-kernel@...r.kernel.org, hpa@...or.com, Paul Mundt <lethal@...ux-sh.org>, rmk@....linux.org.uk, starvik@...s.com, ralf@...ux-mips.org, davem@...emloft.net, cooloney@...nel.org, kyle@...artin.ca, matthew@....cx, grundler@...isc-linux.org, takata@...ux-m32r.org, benh@...nel.crashing.org, rth@...ddle.net, ink@...assic.park.msu.ru, heiko.carstens@...ibm.com Subject: Re: [GIT RFC] percpu: use dynamic percpu allocator as the default percpu allocator On Tue, 31 Mar 2009, Martin Schwidefsky wrote: > I got the dynamic cpu allocator to work with the patch below. Anybody > with an objection against the SHIFT_PERCPU_VAR macro ? Please include the patch inline next time. Why is there a difference between percpu alloc and "static" percpu variables? The "static" percpu variables can be dynamically allocated when a module is loaded. Isnt this mmore an issue that can be addressed by changing the way the initial per cpu segment is allocated? If its also dynamically allocated then there should be no problem? -- 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