Thread (5 messages) 5 messages, 3 authors, 2011-09-27

Re: [RFC][PATCH] slab: fix caller tracking onCONFIG_OPTIMIZE_INLINING.

From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Date: 2011-09-25 05:23:30

David Rientjes wrote:
On Sat, 24 Sep 2011, Tetsuo Handa wrote:
quoted
If CONFIG_OPTIMIZE_INLINING=y, /proc/slab_allocators shows entries like

  size-512: 5 kzalloc+0xb/0x10
  size-256: 31 kzalloc+0xb/0x10

which are useless for debugging.
This is only an issue for gcc 4.x compilers, correct?
Yes.
So this is going against the inlining algorithms in gcc 4.x which will 
make the kernel image significantly larger even though there seems to be 
no benefit unless you have CONFIG_DEBUG_SLAB_LEAK, although this patch 
changes behavior for every system running CONFIG_SLAB with tracing 
support.
If use of address of kzalloc() itself is fine for tracing functionality, we
don't need to force tracing functionality to use caller address of kzalloc().

I merely want /proc/slab_allocators to print caller address of kzalloc() rather
than kzalloc() address itself.

--
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>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help