Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: [PATCH] x86_64: Make NR_IRQS configurable in Kconfig
Date: Mon, 7 Aug 2006 11:23:16 -0500
Message-ID: <19D0D50E9B1D0A40A9F0323DBFA04ACC023B0C87@USRV-EXCH4.na.uis.unisys.com>
In-Reply-To: <200608071817.13318.ak@suse.de>
Thread-Topic: [PATCH] x86_64: Make NR_IRQS configurable in Kconfig
Thread-Index: Aca6PPfRXsGrZ8xWTiq0S68dLxef1gAABV/g
From: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
To: "Andi Kleen" <ak@suse.de>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
       "Eric W. Biederman" <ebiederm@xmission.com>,
       "Andrew Morton" <akpm@osdl.org>, <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 957
Lines: 27


> > 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.
> 
Yes, evaluating dynamically would be best... Should be ACPI job I
suppose, including accounting of all possible hot plug controllers.
Unisys boxes have plenty of them, I can look into possible scenarios.

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