Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753221AbZJZQiI (ORCPT ); Mon, 26 Oct 2009 12:38:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751553AbZJZQiH (ORCPT ); Mon, 26 Oct 2009 12:38:07 -0400 Received: from cantor2.suse.de ([195.135.220.15]:58148 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751499AbZJZQiG (ORCPT ); Mon, 26 Oct 2009 12:38:06 -0400 Date: Mon, 26 Oct 2009 17:38:07 +0100 (CET) From: Jiri Kosina X-X-Sender: jikos@twin.jikos.cz To: Ingo Molnar Cc: "Luck, Tony" , Tejun Heo , Jeff Mahoney , Peter Zijlstra , Linux Kernel Mailing List , "Yu, Fenghua" , "linux-ia64@vger.kernel.org" Subject: Re: Commit 34d76c41 causes linker errors on ia64 with NR_CPUS=4096 In-Reply-To: Message-ID: References: <4ADD54D4.70808@kernel.org> <4ADD5530.3050107@kernel.org> <4ADDC69A.5000701@suse.com> <4ADDCDED.6060706@suse.com> <20091021061109.GA27195@elte.hu> <4ADF2691.7070304@kernel.org> <57C9024A16AD2D4C97DC78E552063EA3E337CF79@orsmsx505.amr.corp.intel.com> <57C9024A16AD2D4C97DC78E552063EA3E337D94C@orsmsx505.amr.corp.intel.com> <20091023075151.GB10067@elte.hu> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) 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: 1624 Lines: 41 On Fri, 23 Oct 2009, Jiri Kosina wrote: > > > > Tony, is the change that will eventually have to be made to ia64 > > > > pagefault handler too intrusive for -rc6, and should we rather go > > > > with my workaround instead, and try to find something proper for > > > > 2.6.33? > > > > > > Using __alloc_percpu() rather than static declaration looks to be the > > > right fix here. Not a "workaround". > > > > It is a workaround for the IA64 build failure. > > > > It's also an improvement of the scheduler code (we generally try to > > eliminate NR_CPUs scaling of allocations) - but code improvements need > > to happen much sooner than -rc6/-rc7. > > Unfortunately refactoring the ia4 pagefault handler would require some > refactoring in order to eliminate the 64k limitation, as far as I know, > which doesn't seem to be feasible for this timeframe either. > > So if I personally have to chose from these two options, I'd prefer my > patch for 2.6.32 and it'd be helpful if ia64 people could look into doing > something with the 64k limit for 2.6.33. > > Acceptable for everyone? Ingo/Peter, will you merge this asap please, so > that we don't miss 2.6.32 with it? This stil seems unfixed in the relevant trees I have checked ... anyone has strong objections to this, which cause the patch to be delayed? Thanks, -- Jiri Kosina SUSE Labs, Novell Inc. -- 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/