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: <m11wrsfsma.fsf@ebiederm.dsl.xmission.com>
Date:	Mon, 07 Aug 2006 09:55:09 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Andi Kleen <ak@...e.de>
Cc:	Andrew Morton <akpm@...l.org>,
	"Protasevich, Natalie" <Natalie.Protasevich@...sys.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86_64: Make NR_IRQS configurable in Kconfig

Andi Kleen <ak@...e.de> writes:

> On Monday 07 August 2006 17:26, Eric W. Biederman wrote:
>> 
>> Currrently on a SMP system we can theoretically support
>> NR_CPUS*224 irqs.  Unfortunately our data structures
>> don't cope will with that many irqs, nor does hardware
>> typically provide that many irq sources.
>> 
>> With the number of cores starting to follow Moores
>> law, and the apicid limits being raised beyond an 8bit
>> number trying to track our current maximum with our
>> current data structures would be fatal and wasteful.
>> 
>> So this patch decouples the number of irqs we support
>> from the number of cpus.  We can revisit this decision
>> once someone reworks the current data structures.
>
> Ok. I was about to apply it, but it seems to require
> mm patches right now, so i didn't

Right.  This is post 2.6.18 material, that is getting
the final bug fixes now.  So it will be ready when 2.6.19 opens
up.  Andi I just wanted to make certain you saw it. :)

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