From: ebiederm@xmission.com (Eric W. Biederman)
To: "Natalie Protasevich" <protasnb@gmail.com>
Cc: "Len Brown" <lenb@kernel.org>, "Andi Kleen" <ak@suse.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 IOAPIC: de-fang IRQ compression
Date: Wed, 05 Dec 2007 16:25:11 -0700 [thread overview]
Message-ID: <m1mysovi5k.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <32209efe0712050525j486922a9s471f3871e69aedff@mail.gmail.com> (Natalie Protasevich's message of "Wed, 5 Dec 2007 05:25:54 -0800")
"Natalie Protasevich" <protasnb@gmail.com> writes:
> On Nov 27, 2007 10:21 PM, Len Brown <lenb@kernel.org> wrote:
>> commit c434b7a6aedfe428ad17cd61b21b125a7b7a29ce
>> (x86: avoid wasting IRQs for PCI devices)
>> created a concept of "IRQ compression" on i386
>> to conserve IRQ numbers on systems with many
>> sparsely populated IO APICs.
>>
>> The same scheme was also added to x86_64,
>> but later removed when x86_64 recieved an IRQ over-haul
>> that made it unnecessary -- including per-CPU
>> IRQ vectors that greatly increased the IRQ capacity
>> on the machine.
>>
>> i386 has not received the analogous over-haul,
>> and thus a previous attempt to delete IRQ compression
>> from i386 was rejected on the theory that there may
>> exist machines that actually need it. The fact is
>> that the author of IRQ compression patch was unable
>> to confirm the actual existence of such a system.
>
> Those systems did exist (and still exist actually). They used over 200
> irqs sometimes and with "normal" IRQ allocation they were failing even
> before reaching half of their I/O configuration. So simple removal
> wouldn't work for those, dynamic allocation sure would. They "scrolled
> off the topic" though because new generations of such machines are not
> 32 bit anymore. So the author didn't actually object :) it was the
> other users of large 32 bit platforms that did.
Natalie. Did they just have over 200 irqs/gsis or did they actually
use over 200 irqs?
In particular is a large NR_IRQS plus dynamic vector allocation
sufficient for all cases you know about?
Eric
next prev parent reply other threads:[~2007-12-05 23:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 6:21 Len Brown
2007-11-28 7:09 ` Eric W. Biederman
2007-12-04 12:26 ` Ingo Molnar
2007-12-04 18:46 ` Eric W. Biederman
2007-12-04 20:55 ` Christian Kujau
2007-12-04 21:28 ` Ingo Molnar
2007-12-05 0:39 ` Andrew Morton
2007-12-05 9:48 ` Ingo Molnar
2007-12-07 2:41 ` Len Brown
2007-12-07 19:16 ` Eric W. Biederman
2007-12-07 20:26 ` Ingo Molnar
2007-12-07 20:31 ` Ingo Molnar
2007-12-07 21:09 ` Eric W. Biederman
2007-12-05 13:25 ` Natalie Protasevich
2007-12-05 23:25 ` Eric W. Biederman [this message]
2007-12-05 23:48 ` Natalie Protasevich
2007-12-06 2:20 ` 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=m1mysovi5k.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=protasnb@gmail.com \
--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
Powered by JetHome