From: Ashok Raj <ashok.raj@intel.com>
To: Natalie.Protasevich@unisys.com
Cc: akpm@osdl.org, ak@suse.de, zwane@arm.linux.org.uk, "Brown,
Len" <len.brown@intel.com>,
bjorn.helgaas@hp.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/1] Proposed: Let's not waste precious IRQs...
Date: Fri, 20 May 2005 06:45:32 -0700 [thread overview]
Message-ID: <20050520064531.A14497@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050519110613.B817D27266@linux.site>; from Natalie.Protasevich@unisys.com on Thu, May 19, 2005 at 04:06:13AM -0700
Hi Natalie,
have you taken a look a the Vector Sharing Patch posted by Kaneshige for IA64?
Cheers,
ashok
On Thu, May 19, 2005 at 04:06:13AM -0700, Natalie.Protasevich@unisys.com wrote:
>
> I suggest to change the way IRQs are handed out to PCI devices.
> Currently, each I/O APIC pin gets associated with an IRQ, no matter if
> the pin is used or not. It is expected that each pin can potentually
> be engaged by a device inserted into the corresponding PCI slot.
> However, this imposes severe limitation on systems that have designs
> that employ many I/O APICs, only utilizing couple lines of each, such
> as P64H2 chipset. It is used in ES7000, and currently, there is no way
> to boot the system with more that 9 I/O APICs. The simple change below
> allows to boot a system with say 64 (or more) I/O APICs, each
> providing 1 slot, which otherwise impossible because of the IRQ gaps
> created for unused lines on each I/O APIC. It does not resolve the
> problem with number of devices that exceeds number of possible IRQs,
> but eases up a tension for IRQs on any large system with potentually
> large number of devices. I only implemented this for the ACPI boot,
> since if the system is this big and
>.. deleted...
next prev parent reply other threads:[~2005-05-20 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 11:06 [patch 1/1] Proposed: Let's not waste precious IRQs Natalie.Protasevich
2005-05-20 13:45 ` Ashok Raj [this message]
2005-05-20 20:26 ` Bjorn Helgaas
2005-05-20 17:03 ` Zwane Mwaikambo
2005-05-20 19:39 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-05-20 16:34 Protasevich, Natalie
2005-05-20 17:27 Protasevich, Natalie
2005-05-20 21:14 Protasevich, Natalie
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=20050520064531.A14497@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=Natalie.Protasevich@unisys.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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