From: ebiederm@xmission.com (Eric W. Biederman)
To: Len Brown <lenb@kernel.org>
Cc: Andi Kleen <ak@suse.de>,
Natalie Protasevich <Natalie.Protasevich@unisys.com>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH] i386: irq: Kill IRQ compression
Date: Fri, 16 Feb 2007 00:44:07 -0700 [thread overview]
Message-ID: <m1wt2ih7i0.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200702160015.04453.lenb@kernel.org> (Len Brown's message of "Fri, 16 Feb 2007 00:15:04 -0500")
Len Brown <lenb@kernel.org> writes:
> This code makes simple systems complex:
>
> ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 18 (level, low) -> IRQ 16
> ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 17
> ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 18
> ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 19
>
> The same code was already removed from x86_64
By itself I don't think we are going to observe any real problems
with this patch.
However if we are going to be serious about this we need to do a
few more things.
- kill iopaic_renumber_irq.
- Increase NR_IRQS.
We will still be limited to about 208 interrupts in use at one
time, but we can allow more irq sources to be described.
This reminds me. I really need to dig up my patch that doesn't
allocate a vector for an irq until request irq time.
Eric
next prev parent reply other threads:[~2007-02-16 7:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 5:15 [PATCH] i386: irq: Kill IRQ compression Len Brown
2007-02-16 7:44 ` Eric W. Biederman [this message]
2007-02-16 9:21 ` Eric W. Biederman
2007-02-16 9:51 ` [PATCH] i386 irq: Kill NR_IRQ_VECTORS and increase NR_IRQS Eric W. Biederman
2007-02-16 10:15 ` Andi Kleen
2007-02-16 10:33 ` Eric W. Biederman
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=m1wt2ih7i0.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=Natalie.Protasevich@unisys.com \
--cc=ak@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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