On Tue, 28 Jun 2011, David Daney wrote:

On 06/28/2011 12:32 PM, Christoph Lameter wrote:

quoted

On Sun, 26 Jun 2011, Marcin Slusarz wrote:

quoted

slub checks for poison one byte by one, which is highly inefficient
and shows up frequently as a highest cpu-eater in perf top.

Ummm.. Performance improvements for debugging modes? If you need
performance then switch off debuggin.

There is no reason to make things gratuitously slow.  I don't know about the
merits of this particular patch, but I must disagree with the general
sentiment.

We have high performance tracing, why not improve this as well.

Just last week I was trying to find the cause of memory corruption that only
occurred at very high network packet rates.  Memory allocation speed was
definitely getting in the way of debugging.  For me, faster SLUB debugging
would be welcome.

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.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  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@kvack.org"> email@kvack.org </a>