linux-kernel - Re: [PATCH] sparse_irq aka dyn

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 for Android: free password hash cracker in your pocket

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

Message-ID: <491CEB23.80403@sgi.com>
Date:	Thu, 13 Nov 2008 19:06:11 -0800
From:	Mike Travis <travis@....com>
To:	David Miller <davem@...emloft.net>
CC:	paulus@...ba.org, akpm@...ux-foundation.org, yinghai@...nel.org,
	mingo@...e.hu, tglx@...utronix.de, hpa@...or.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sparse_irq aka dyn_irq v13

David Miller wrote:

> Practicality is what really matters.
> 
> We can even make the constant number a config option, so that if
> someone has a system that actually triggers past this limit even dist
> vendors can simply bump the config option value.

Unfortunately the reality is that distros spend months certifying the base
kernel for both application and security conformance.  And many (most?) of
the large system customers will only run this kernel.  Even changing root
startup options is considered invalidating the conformance testing.  That
means the kernel has to adapt to the resource needs of the system being
serviced.

Ideally, linux shouldn't have any fixed resources.  A system built to run
on a massively parallel system should also boot and run on a smart phone
(not well perhaps... ;-)
--
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/