linux-kernel - RE: [PATCH] x86_64: Make NR_IRQS configurable in Kconfig

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19D0D50E9B1D0A40A9F0323DBFA04ACC023B0C87@USRV-EXCH4.na.uis.unisys.com>
Date:	Mon, 7 Aug 2006 11:23:16 -0500
From:	"Protasevich, Natalie" <Natalie.Protasevich@...SYS.com>
To:	"Andi Kleen" <ak@...e.de>
Cc:	"Randy.Dunlap" <rdunlap@...otime.net>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"Andrew Morton" <akpm@...l.org>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] x86_64: Make NR_IRQS configurable in Kconfig


> > 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/