| 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: Tue, 8 May 2007 19:33:23 -0500 From: Matt Mackall <mpm@...enic.com> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, clameter@....com Subject: Re: + fix-spellings-of-slab-allocator-section-in-init-kconfig.patch added to -mm tree On Wed, May 09, 2007 at 01:32:20AM +0100, Alan Cox wrote: > > (without SLAB emulation) and fragmentation was not the driving force > > for replacement. Small Linux 1.x machines frequently had uptimes of 1+ > > years without fragmenting to death. Instead, it was performance with > > 8MB for a bit over 3 years.... (1.2.13lmp) > > The fragmentation issue I think is overbaked. A lot of the academic work > argues that there is pretty much no long term difference between first > fit, best fit, and most of the clever algorithms (obviously stupid ones > like "take the middle out of the biggest space allocator" do perform > worse). For MMUless boxes fragmentation is a big issue but not for normal > systems. Further, the received wisdom that fragmentation of SLAB-like systems is better is not above doubt. Our own issues with dcache fragmentation suggest it's far from perfect. -- Mathematics is the supreme nostalgia of our time. - 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