From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Luck, Tony" <tony.luck@intel.com>, Ingo Molnar <mingo@elte.hu>,
Mike Travis <travis@sgi.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
"isimatu.yasuaki@jp.fujitsu.com" <isimatu.yasuaki@jp.fujitsu.com>
Subject: Re: [PATCH 0/8] git pull request for tip/tracing/core
Date: Thu, 12 Feb 2009 12:15:35 +0900 [thread overview]
Message-ID: <49939457.7030001@jp.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0902112142050.13954@gandalf.stny.rr.com>
Steven Rostedt wrote:
> On Thu, 12 Feb 2009, Kenji Kaneshige wrote:
>> Luck, Tony wrote:
>>>>> Before we go and make the change, Peter brought up a good point on IRC. Is
>>>>> there any reason that ia64 needs 1 << 14 IRQs? That's 16384!
>>>>>
>>>>> Perhaps the better solution wolud be (if possible), to simply lower the
>>>>> number of bits.
>>>> i'm the wrong person to be asked about that. (Cc:-ed the right people)
>>> People build some pretty big systems on ia64. SGI's largest has 4096
>>> cpus ... so 16384 IRQs is only 4 per cpu. That doesn't sound like very
>>> many to me.
>>>
>>> Fujitsu added the vector domain support for ia64 to get around the shortage
>>> of IRQs for large machines. Added them to the Cc: list to see if they have
>>> comments on how many IRQs are needed.
>>>
>> The 1024 IRQs are enough for GSIs on our maximum configuration. But
>> if the devices are MSI/MSI-X capable, it could be more than 1024.
>
> But you would never expect more than 1024 nested interrupts all on the
> same CPU? That is, to have over 1024 interrupts interrupting each other?
>
Itanium processor has 240 vectors for external interrupts and
has a mechanism to classifies them to 16 priority classes. The
ia64 linux limits maximum nested interrupts depth to 16 using
this mechanism.
Thanks,
Kenji Kaneshige
next prev parent reply other threads:[~2009-02-12 3:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 5:49 [PATCH 0/8] git pull request for tip/tracing/core Steven Rostedt
2009-02-08 5:49 ` [PATCH 1/8] trace: remove deprecated entry->cpu Steven Rostedt
2009-02-08 12:29 ` Frederic Weisbecker
2009-02-08 5:49 ` [PATCH 2/8] ring-buffer: add NMI protection for spinlocks Steven Rostedt
2009-02-08 5:49 ` [PATCH 3/8] ring-buffer: allow tracing_off to be used in core kernel code Steven Rostedt
2009-02-08 5:49 ` [PATCH 4/8] ftrace, x86: rename in_nmi variable Steven Rostedt
2009-02-08 5:50 ` [PATCH 5/8] nmi: add generic nmi tracking state Steven Rostedt
2009-02-08 5:50 ` [PATCH 6/8] ftrace: change function graph tracer to use new in_nmi Steven Rostedt
2009-02-08 5:50 ` [PATCH 7/8] ring-buffer: use generic version of in_nmi Steven Rostedt
2009-02-08 5:50 ` [PATCH 8/8] trace: trivial fixes in comment typos Steven Rostedt
2009-02-09 9:37 ` [PATCH 0/8] git pull request for tip/tracing/core Ingo Molnar
2009-02-11 15:36 ` Ingo Molnar
2009-02-11 15:46 ` Steven Rostedt
2009-02-11 16:25 ` Ingo Molnar
2009-02-11 16:33 ` Steven Rostedt
2009-02-11 16:49 ` Steven Rostedt
2009-02-11 16:59 ` Steven Rostedt
2009-02-11 17:16 ` Ingo Molnar
2009-02-11 17:30 ` Steven Rostedt
2009-02-11 17:31 ` Ingo Molnar
2009-02-11 17:57 ` Luck, Tony
2009-02-11 18:23 ` Steven Rostedt
2009-02-11 18:34 ` Luck, Tony
2009-02-11 18:42 ` Steven Rostedt
2009-02-11 20:20 ` Ingo Molnar
2009-02-11 20:39 ` Jack Steiner
2009-02-12 2:39 ` Kenji Kaneshige
2009-02-12 2:43 ` Steven Rostedt
2009-02-12 3:15 ` Kenji Kaneshige [this message]
2009-02-12 3:22 ` Steven Rostedt
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=49939457.7030001@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=travis@sgi.com \
/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