From: David Laight <David.Laight@ACULAB.COM>
To: 'George Cherian' <george.cherian@marvell.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "sgoutham@marvell.com" <sgoutham@marvell.com>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: RE: [PATCH] genirq: Increase the number of interrupters
Date: Thu, 23 Jun 2022 11:18:14 +0000 [thread overview]
Message-ID: <7974b4d7782b4f8682547389d4f294f8@AcuMS.aculab.com> (raw)
In-Reply-To: <20220623031541.1716745-1-george.cherian@marvell.com>
From: George Cherian
> Sent: 23 June 2022 04:16
>
> Currently the maximum number of interrupters is capped at 8260 (64 +
> 8196) in most of the architectures were CONFIG_SPARSE_IRQ is selected.
> This upper limit is not sufficient for couple of existing SoC's from
> Marvell.
> For eg: Octeon TX2 series of processors support a maximum of 32K
> interrupters.
>
> Bump up the upper limit from 8196 to 65536.
This seems to add 7kB of static data to the kernel just on
the off chance that some sparse interrupt numbers are large.
David
>
> Signed-off-by: George Cherian <george.cherian@marvell.com>
> ---
> kernel/irq/internals.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/irq/internals.h b/kernel/irq/internals.h
> index f09c60393e559..9bb42757d4afc 100644
> --- a/kernel/irq/internals.h
> +++ b/kernel/irq/internals.h
> @@ -12,7 +12,7 @@
> #include <linux/sched/clock.h>
>
> #ifdef CONFIG_SPARSE_IRQ
> -# define IRQ_BITMAP_BITS (NR_IRQS + 8196)
> +# define IRQ_BITMAP_BITS (NR_IRQS + 65536)
> #else
> # define IRQ_BITMAP_BITS NR_IRQS
> #endif
> --
> 2.25.1
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-06-23 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 3:15 George Cherian
2022-06-23 11:18 ` David Laight [this message]
2022-06-27 4:53 ` George Cherian
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=7974b4d7782b4f8682547389d4f294f8@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=george.cherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sgoutham@marvell.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
all inboxes | Powered by JetHome®