On Tue, 28 Jun 2011, Ben Greear wrote: > > SLUB debugging is useful only to diagnose issues or test new code, nobody > > is going to be enabling it in production environment. We don't need 30 > > new lines of code that make one thing slightly faster, in fact we'd prefer > > to have as simple and minimal code as possible for debugging features > > unless you're adding more debugging coverage. > > If your problem happens under load, then the overhead of slub could > significantly > change the behaviour of the system. You're talking about slub debugging and not slub in general, I assume. > Anything that makes it more efficient > without > unduly complicating code should be a win. That posted patch wasn't all that > complicated, and even if it has bugs, it could be fixed easily enough. > "Even if it has bugs"? Ask Pekka to merge this and be on the receiving end of every other kernel development's flames when slub debugging no longer finds their problems but instead has bugs of its own. Again, we want simple and minimal slub debugging code unless you're adding a new feature. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>