From: "Yinghai Lu" <yinghai@kernel.org>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: make 32bit MAX_HARDIRQSS_PER_CPU to be NR_VECTORS
Date: Wed, 14 Jan 2009 13:38:20 -0800 [thread overview]
Message-ID: <86802c440901141338m78233d09y99d79be98eea4cba@mail.gmail.com> (raw)
In-Reply-To: <20090114111755.GN2913@elte.hu>
On Wed, Jan 14, 2009 at 3:17 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Yinghai Lu <yinghai@kernel.org> wrote:
>
>> Impact: clean up to be same as 64bit
>>
>> 32bit is use per-cpu vector too, so don't use default NR_IRQS
>>
>> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>>
>> ---
>> arch/x86/include/asm/hardirq_32.h | 3 +++
>> arch/x86/include/asm/irq_vectors.h | 4 ++--
>> 2 files changed, 5 insertions(+), 2 deletions(-)
>>
>> Index: linux-2.6/arch/x86/include/asm/hardirq_32.h
>> ===================================================================
>> --- linux-2.6.orig/arch/x86/include/asm/hardirq_32.h
>> +++ linux-2.6/arch/x86/include/asm/hardirq_32.h
>> @@ -20,6 +20,9 @@ typedef struct {
>>
>> DECLARE_PER_CPU(irq_cpustat_t, irq_stat);
>>
>> +/* We can have at most NR_VECTORS irqs routed to a cpu at a time */
>> +#define MAX_HARDIRQS_PER_CPU NR_VECTORS
>> +
>> #define __ARCH_IRQ_STAT
>> #define __IRQ_STAT(cpu, member) (per_cpu(irq_stat, cpu).member)
>
> applied to tip/x86/cleanups. Btw., isnt the irq_vectors.h bit (mentioned
> in the diffstat) missing?
>
copy and modify the patch
forget to do quilt refresh --diffstat
YH
prev parent reply other threads:[~2009-01-14 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 19:54 Yinghai Lu
2009-01-14 11:17 ` Ingo Molnar
2009-01-14 21:38 ` Yinghai Lu [this message]
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=86802c440901141338m78233d09y99d79be98eea4cba@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®