From: William Lee Irwin III <wli@holomorphy.com>
To: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Christoph Hellwig <hch@infradead.org>,
James Cleverdon <jamesclv@us.ibm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] (0/7) Finish moving NUMA-Q into subarch, cleanup
Date: Wed, 15 Jan 2003 12:17:19 -0800 [thread overview]
Message-ID: <20030115201719.GM919@holomorphy.com> (raw)
In-Reply-To: <3FAD1088D4556046AEC48D80B47B478C022BD907@usslc-exch-4.slc.unisys.com>
On Wed, Jan 15, 2003 at 01:30:37PM -0600, Protasevich, Natalie wrote:
> ... and one more from me: isn't it time to let IO-APIC id be 8 bit in the
> asm/io_apic.h (make it a union fot both?..)?
> Look what I have to do in io_apic.h to get around it and ... "mister, have a
> heart":
Point taken; it doesn't burn NUMA-Q, but this probably hits Summit (with
its much more recent APIC and IO-APIC revisions). I don't see why not.
The hardware is there, time to drop in the code to handle it.
At some point in the past, I wrote:
>> There are also somewhat deeper issues with vector assignments to
>> interrupt sources that prevent elevating any of the above to useful
>> levels and utilizing them. The assumptions based on the vector assignment
>> algorithm appear to be widely distributed enough to discourage me after
>> an initial attempt or two to get any kind of useful interrupt routing
>> for a number of IRQ sources larger than the number of vectors.
On Wed, Jan 15, 2003 at 01:30:37PM -0600, Protasevich, Natalie wrote:
> I strongly suggest to take a look in IA64 implementation.
> They have 1:1 correspondence between IRQ and vector and don't seem to be
> able to run out of vectors or IRQs.
Given that almost nothing actually cares what the irq numbers are, it
sounds like a really good idea to encode the node ID in the upper bits
and the vector in the lower bits (SN2 uses cpuid). I'll try it out.
Thanks!
Bill
next prev parent reply other threads:[~2003-01-15 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 19:30 [PATCH] (0/7) Finish moving NUMA-Q into subarch, cleanup Protasevich, Natalie
2003-01-15 20:17 ` William Lee Irwin III [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-15 18:41 Protasevich, Natalie
2003-01-15 18:29 Pallipadi, Venkatesh
2003-01-15 18:37 ` Martin J. Bligh
2003-01-15 19:05 ` William Lee Irwin III
2003-01-13 18:19 Protasevich, Natalie
2003-01-13 18:30 ` Martin J. Bligh
2003-01-07 20:44 Martin J. Bligh
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=20030115201719.GM919@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=hch@infradead.org \
--cc=jamesclv@us.ibm.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=venkatesh.pallipadi@intel.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