From: Pavel Vasilyev <pavel@pavlinux.ru>
To: LKML <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] asm-generic: Raise default NR_IRQS when using sparse IRQs
Date: Mon, 29 Nov 2010 23:02:53 +0300 [thread overview]
Message-ID: <4CF406ED.6070705@pavlinux.ru> (raw)
In-Reply-To: <fUhqx-3EE-15@gated-at.bofh.it>
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.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> include/asm-generic/irq.h | 6 +++++-
> 1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/include/asm-generic/irq.h b/include/asm-generic/irq.h
> index b90ec0b..0d95650 100644
> --- a/include/asm-generic/irq.h
> +++ b/include/asm-generic/irq.h
> @@ -4,11 +4,15 @@
> /*
> * NR_IRQS is the upper bound of how many interrupts can be handled
> * in the platform. It is used to size the static irq_map array,
> - * so don't make it too big.
> + * so don't make it too big unless we're using sparse IRQs.
> */
> #ifndef NR_IRQS
> +#ifdef CONFIG_SPARSE_IRQ
> +#define NR_IRQS 0xffff
> +#else
> #define NR_IRQS 64
> #endif
> +#endif
>
> static inline int irq_canonicalize(int irq)
> {
May be
#define NR_IRQS 15*NR_CPUS
next parent reply other threads:[~2010-11-29 20:02 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 ` Pavel Vasilyev [this message]
2010-11-29 21:53 ` [PATCH] asm-generic: Raise default NR_IRQS when using sparse IRQs Mark Brown
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=4CF406ED.6070705@pavlinux.ru \
--to=pavel@pavlinux.ru \
--cc=broonie@opensource.wolfsonmicro.com \
--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