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
| ||
|
Date: Sat, 8 Aug 2009 12:14:39 +0300 From: Al Boldi <a1426z@...ab.com> To: Greg KH <greg@...ah.com> Cc: Chris Friesen <cfriesen@...tel.com>, Andi Kleen <andi@...stfloor.org>, Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org, Kay Sievers <kay.sievers@...y.org>, Jan Blunck <jblunck@...e.de>, gregkh@...e.de, Harald Hoyer <harald@...hat.com>, Scott James Remnant <scott@...ntu.com> Subject: Re: [PATCH] Driver Core: devtmpfs - kernel-maintained tmpfs-based /dev Greg KH wrote: > On Sat, Aug 08, 2009 at 12:17:31AM +0300, Al Boldi wrote: > > For devtmpfs to be a realistic replacement for static /dev, it has to > > be comparable to static /dev in both speed and size. > > Since when is this requirement necessary? You want something for free > in both speed and size? Well, you got it in speed, but not size, it > will take up memory that is swapable, and a tiny ammount of non-swapable > kernel memory for the code. Not so tiny when you count in the hotplug dependency. > > WRT speed, there should be no slowdown and it should be just as fast > > as a "tar -xp < dev.tar". > > Again, where is this requirement coming from? > > Have you timed devtmpfs? Not yet, I am still waiting for the latest patch against .30. > > WRT size, it should not be dependent on hotplug, and instead offer > > hotplug as an option. > > Um, again, who made up such a requirement? Are you running systems > today with CONFIG_HOTPLUG disabled? If so, how well is that working for > you? It's working out quite well. I don't like hotplug, it's too slow. I always turn it and module-autoloading off, to achieve a much more responsive system. Thanks! -- Al -- 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/
Powered by blists - more mailing lists