summaryrefslogtreecommitdiff
path: root/lib
diff options
context:
space:
mode:
authorStephen Rothwell <sfr@canb.auug.org.au>2008-12-03 14:34:08 +1100
committerStephen Rothwell <sfr@canb.auug.org.au>2008-12-03 14:34:08 +1100
commit9f0f65001e031a28e3ac6bbcf775861ce6ec2dff (patch)
tree248cfcf0469f9dfd5628579e9209b81df6dc23e4 /lib
parent914ef0ae6aee5ca841e550d5d60907fe5ed5a60d (diff)
parent00f39605364d5d04d669c7c280d8645efee3aa51 (diff)
Merge commit 'slab/for-next'
Diffstat (limited to 'lib')
-rw-r--r--lib/Kconfig.debug20
1 files changed, 20 insertions, 0 deletions
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 1e3fd3e3436a..7854bc8ac596 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -813,6 +813,26 @@ config FIREWIRE_OHCI_REMOTE_DMA
If unsure, say N.
+config KMEMTRACE
+ bool "Kernel memory tracer (kmemtrace)"
+ depends on RELAY && DEBUG_FS && MARKERS
+ help
+ kmemtrace provides tracing for slab allocator functions, such as
+ kmalloc, kfree, kmem_cache_alloc, kmem_cache_free etc.. Collected
+ data is then fed to the userspace application in order to analyse
+ allocation hotspots, internal fragmentation and so on, making it
+ possible to see how well an allocator performs, as well as debug
+ and profile kernel code.
+
+ This requires an userspace application to use. See
+ Documentation/vm/kmemtrace.txt for more information.
+
+ Saying Y will make the kernel somewhat larger and slower. However,
+ if you disable kmemtrace at run-time or boot-time, the performance
+ impact is minimal (depending on the arch the kernel is built for).
+
+ If unsure, say N.
+
menuconfig BUILD_DOCSRC
bool "Build targets in Documentation/ tree"
depends on HEADERS_CHECK