Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751208AbWHHCSH (ORCPT ); Mon, 7 Aug 2006 22:18:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751209AbWHHCSH (ORCPT ); Mon, 7 Aug 2006 22:18:07 -0400 Received: from mail.suse.de ([195.135.220.2]:14756 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S1751208AbWHHCSG (ORCPT ); Mon, 7 Aug 2006 22:18:06 -0400 From: Andi Kleen To: Andrew Morton Subject: Re: [PATCH] x86_64: Make NR_IRQS configurable in Kconfig Date: Tue, 8 Aug 2006 04:17:59 +0200 User-Agent: KMail/1.9.3 Cc: "Eric W. Biederman" , "Randy.Dunlap" , "Protasevich, Natalie" , linux-kernel@vger.kernel.org References: <20060807165512.dabefb63.akpm@osdl.org> In-Reply-To: <20060807165512.dabefb63.akpm@osdl.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608080417.59462.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 924 Lines: 23 > > And it's a pretty nasty one because it can get people into the situation > where the kernel worked fine for those who released it, but users who > happen to load more modules (or the right combination of them) will > experience per-cpu memory exhaustion. Yes, and a high value will waste a lot of memory for normal users. > So shouldn't we being scaling the per-cpu memory as well? If we move it into vmalloc space it would be easy to extend at runtime - just the virtual address space would need to be prereserved, but then more pages could be mapped. Maybe we should just do that instead of continuing to kludge around? Drawback would be some more TLB misses. -Andi - 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/