Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762662AbZCaR0Y (ORCPT ); Tue, 31 Mar 2009 13:26:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755826AbZCaR0P (ORCPT ); Tue, 31 Mar 2009 13:26:15 -0400 Received: from smtp.ultrahosting.com ([74.213.174.254]:45022 "EHLO smtp.ultrahosting.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754634AbZCaR0O (ORCPT ); Tue, 31 Mar 2009 13:26:14 -0400 Date: Tue, 31 Mar 2009 13:20:42 -0400 (EDT) From: Christoph Lameter X-X-Sender: cl@qirst.com To: Martin Schwidefsky cc: Tejun Heo , Ingo Molnar , rusty@rustcorp.com.au, tglx@linutronix.de, x86@kernel.org, linux-kernel@vger.kernel.org, hpa@zytor.com, Paul Mundt , rmk@arm.linux.org.uk, starvik@axis.com, ralf@linux-mips.org, davem@davemloft.net, cooloney@kernel.org, kyle@mcmartin.ca, matthew@wil.cx, grundler@parisc-linux.org, takata@linux-m32r.org, benh@kernel.crashing.org, rth@twiddle.net, ink@jurassic.park.msu.ru, heiko.carstens@de.ibm.com Subject: Re: [GIT RFC] percpu: use dynamic percpu allocator as the default percpu allocator In-Reply-To: <20090331185431.72ff1707@skybase> Message-ID: References: <1236671631-9305-1-git-send-email-tj@kernel.org> <20090316190132.7965a49a@skybase> <49C300D8.5080204@kernel.org> <49C8FAC4.6060508@kernel.org> <20090325122738.42d105b7@skybase> <49CA1AC3.9080908@kernel.org> <20090325122241.GE11571@elte.hu> <49CA2345.70204@kernel.org> <20090325141330.2717dc97@skybase> <49CA2FBF.9000207@kernel.org> <20090325142525.2d31c522@skybase> <49CA32F6.2030408@kernel.org> <20090331185431.72ff1707@skybase> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 808 Lines: 21 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/