On Tue, 25 May 2010, Pekka Enberg wrote: > I wouldn't say it's a nightmare, but yes, it could be better. From my > point of view SLUB is the base of whatever the future will be because > the code is much cleaner and simpler than SLAB. The code may be much cleaner and simpler than slab, but nobody (to date) has addressed the significant netperf TCP_RR regression that slub has, for example. I worked on a patchset to do that for a while but it wasn't popular because it added some increments to the fastpath for tracking data. I think it's great to have clean and simple code, but even considering its use is a non-starter when the entire kernel is significantly slower for certain networking loads. > That's why I find > Christoph's work on SLEB more interesting than SLQB, for example, > because it's building on top of something that's mature and stable. > > That said, are you proposing that even without further improvements to > SLUB, we should go ahead and, for example, remove SLAB from Kconfig > for v2.6.36 and see if we can just delete the whole thing from, say, > v2.6.38? > We use slab internally specifically because of the slub regressions. Removing it from the kernel at this point would be the equivalent of saying that Linux cares about certain workloads more than others since there are clearly benchmarks that show slub to be inferior in pure performance numbers. I'd love for us to switch to slub but we can't take the performance hit. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>