linux-kernel - Re: [PATCH] asm-generic: Raise default NR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20101129215134.GA8335@opensource.wolfsonmicro.com>
Date:	Mon, 29 Nov 2010 21:53:28 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Pavel Vasilyev <pavel@...linux.ru>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] asm-generic: Raise default NR_IRQS when using sparse
 IRQs

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/