linux-kernel - Re: CONFIG_IRQBALANCE for 64-bit x86 ?

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 20 Nov 2007 15:28:45 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Mark Lord <lkml@....ca>
CC:	Ingo Molnar <mingo@...e.hu>,
	Arjan van de Ven <arjan@...radead.org>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...l.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: CONFIG_IRQBALANCE for 64-bit x86 ?

Mark Lord wrote:
> 
> Perhaps, but this also violates the principle that the kernel
> should just *work* with sensible defaults.  I don't use an initrd,
> or an initramfs, and have no intention of ever doing so.
> 
> I *like* having a single boot image with no unneeded/unwanted complexity.
> It's only recently that I've even come round to using some loadable
> modules for things like network drivers -- I prefer a single image
> for as much as possible (like Linus there).
> 
> If putting a C-library and utilities "into the kernel" still leaves
> me with a single image file, then.. maybe.  Seems clumsy, though.
> 

That was the whole point of klibc, and in fact it was in -mm that way 
for a while.  Linus rejected it at the time on the grounds that it added 
no new features, only moved existing features to userspace.

The unified build tree has since then bitrotted slightly due to lack of 
time on my part, but it wouldn't be hard at all to bring it up to current.

	-hpa
-
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/