From: Andi Kleen <ak@suse.de>
To: "Protasevich, Natalie" <Natalie.Protasevich@unisys.com>
Subject: Re: [PATCH] x86_64: Make NR_IRQS configurable in Kconfig
Date: Mon, 7 Aug 2006 18:17:13 +0200
User-Agent: KMail/1.9.3
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
       "Eric W. Biederman" <ebiederm@xmission.com>,
       "Andrew Morton" <akpm@osdl.org>, linux-kernel@vger.kernel.org
References: <19D0D50E9B1D0A40A9F0323DBFA04ACC023B0C86@USRV-EXCH4.na.uis.unisys.com>
In-Reply-To: <19D0D50E9B1D0A40A9F0323DBFA04ACC023B0C86@USRV-EXCH4.na.uis.unisys.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200608071817.13318.ak@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 708
Lines: 19


> 4k being a humble maximum is definitely a relative term here, but on the
> system with "only" 64 or 128 processors the cpu*224 would be much higher
> :) However, maybe CONFIG_TINY that Andi suggested would leverage this
> number also. What do you think, Eric?

Best would be something dynamic - kernels should be self tuning, not 
require that much CONFIG magic.

Just PCI hotplug gives me headaches with this.

Maybe we just need growable per CPU data.

-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/