From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Pavel Vasilyev <pavel@pavlinux.ru>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] asm-generic: Raise default NR_IRQS when using sparse IRQs
Date: Mon, 29 Nov 2010 21:53:28 +0000 [thread overview]
Message-ID: <20101129215134.GA8335@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4CF406ED.6070705@pavlinux.ru>
On Mon, Nov 29, 2010 at 11:02:53PM +0300, Pavel Vasilyev wrote:
> On 29.11.2010 22:20, Mark Brown wrote:
> > Rather than have each platform using sparse IRQs pick a suitably large
> > NR_IRQS for use with sparse IRQs make the default high when they are
> > enabled. We pick 64k as there is still a bitmap of IRQs that is
> > allocated statically, and as we all know 64k should be enough for
> > anyone.
> May be
> #define NR_IRQS 15*NR_CPUS
No, this is missing the point - that's way too low for many systems
(most except x86 I guess). The idea is that since we're using sparse
IRQs we've much less reason to restrict the number of IRQs than we do
when we've got a statically allocated table so we can have a higher
default, meaning less need for platforms to individually select a higher
number.
next prev parent reply other threads:[~2010-11-29 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fUhqx-3EE-15@gated-at.bofh.it>
2010-11-29 20:02 ` [PATCH] asm-generic: Raise default NR_IRQS when using sparse IRQs Pavel Vasilyev
2010-11-29 21:53 ` Mark Brown [this message]
2011-06-29 21:20 Mark Brown
2011-06-30 7:27 ` Thomas Gleixner
2011-06-30 15:13 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2010-11-29 19:17 Mark Brown
2010-11-24 15:39 Mark Brown
2010-11-24 15:45 ` Thomas Gleixner
2010-11-24 15:56 ` Mark Brown
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=20101129215134.GA8335@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@pavlinux.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.