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 19:20:52 -0700 [thread overview]
Message-ID: <m1eje0va0r.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <32209efe0712051548n72f60b0eofa130f28701ca77@mail.gmail.com> (Natalie Protasevich's message of "Wed, 5 Dec 2007 15:48:28 -0800")
"Natalie Protasevich" <protasnb@gmail.com> writes:
> I think we counted them in the order of 1400 external IRQs (actual
> ioapics/slots plus possible on-card bridges), and yes numbers for used
> IRQs were close to 250. Actual customer configurations could've big
> bigger, I don't have such data.
>
>> In particular is a large NR_IRQS plus dynamic vector allocation
>> sufficient for all cases you know about?
>
> Yes, since x86_64 boxes never had a problem once dynamic vectors were
> incorporated.
I was wondering if we could avoid making the vectors per cpu and still be
in good shape on x86_32. From your description it looks like we can't
quite support everything on x86_32 if we don't do the per cpu vector
thing. However we will likely have everything interesting supported.
Eric
prev parent reply other threads:[~2007-12-06 2:23 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
2007-12-05 23:48 ` Natalie Protasevich
2007-12-06 2:20 ` Eric W. Biederman [this message]
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=m1eje0va0r.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