From: ebiederm@xmission.com (Eric W. Biederman)
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
"Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: Make NR_IRQS configurable in Kconfig
Date: Mon, 07 Aug 2006 12:16:14 -0600 [thread overview]
Message-ID: <m13bc8csy9.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060807105537.08557636.rdunlap@xenotime.net> (Randy Dunlap's message of "Mon, 7 Aug 2006 10:55:37 -0700")
"Randy.Dunlap" <rdunlap@xenotime.net> writes:
>>
>> This of course applies to the -mm tree because the rest
>> of the irq work is not yet in the mainline kernel.
>>
>> arch/x86_64/Kconfig | 14 ++++++++++++++
>> include/asm-x86_64/irq.h | 3 ++-
>> 2 files changed, 16 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/x86_64/Kconfig b/arch/x86_64/Kconfig
>> index 7598d99..cea78d7 100644
>> --- a/arch/x86_64/Kconfig
>> +++ b/arch/x86_64/Kconfig
>> @@ -384,6 +384,20 @@ config NR_CPUS
>> This is purely to save memory - each supported CPU requires
>> memory in the static kernel configuration.
>
> Thanks for the language fixes.
> I'm confused about one thing. What is NR_IRQS for non-SMP?
> Does it default to 4096 or something else?
Right the default is still 4096 which is fairly silly.
> Does this build on non-SMP? Is CONFIG_NR_IRQS defined for non-SMP?
Ugh. I have a "depends on SMP" line in there. That shouldn't be.
Ok. I need to fix the non SMP case, at least take out the dependency
and if I'm clever move the default down to 224.
Eric
next prev parent reply other threads:[~2006-08-07 18:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 15:26 Eric W. Biederman
2006-08-07 15:33 ` Andi Kleen
2006-08-07 15:55 ` Eric W. Biederman
2006-08-07 15:59 ` Randy.Dunlap
2006-08-07 16:11 ` Protasevich, Natalie
2006-08-07 16:17 ` Andi Kleen
2006-08-07 16:23 ` Protasevich, Natalie
2006-08-07 16:58 ` Eric W. Biederman
2006-08-07 16:44 ` Eric W. Biederman
2006-08-07 17:00 ` H. Peter Anvin
2006-08-07 17:46 ` Eric W. Biederman
2006-08-07 17:52 ` H. Peter Anvin
2006-08-07 17:30 ` Eric W. Biederman
2006-08-07 17:55 ` Randy.Dunlap
2006-08-07 18:16 ` Eric W. Biederman [this message]
2006-08-07 18:53 ` Eric W. Biederman
2006-08-07 19:04 ` Randy.Dunlap
2006-08-07 22:10 ` Eric W. Biederman
2006-08-07 23:55 ` Andrew Morton
2006-08-08 2:17 ` Andi Kleen
2006-08-08 2:41 ` Andrew Morton
2006-08-08 2:47 ` Arjan van de Ven
2006-08-08 5:47 ` [PATCH] x86_64: Auto size the per cpu area Eric W. Biederman
2006-08-08 6:01 ` Andrew Morton
2006-08-08 6:31 ` Eric W. Biederman
2006-08-08 6:01 ` Andi Kleen
2006-08-08 6:46 ` Eric W. Biederman
2006-08-08 6:48 ` Andi Kleen
2006-08-08 7:29 ` Eric W. Biederman
2006-08-08 5:09 ` [PATCH] x86_64: Make NR_IRQS configurable in Kconfig Paul Mackerras
2006-08-08 5:14 ` Andi Kleen
2006-08-08 8:17 ` Martin Schwidefsky
2006-08-09 17:58 ` Luck, Tony
2006-08-09 18:25 ` Dave Hansen
2006-08-10 12:55 ` Martin Schwidefsky
2006-08-10 14:40 ` Andy Whitcroft
2006-08-10 14:53 ` Martin Schwidefsky
2006-08-07 19:40 ` Adrian Bunk
2006-08-07 22:26 ` Eric W. Biederman
2006-08-07 23:06 ` Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m13bc8csy9.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome