diff options
author | Stephen Rothwell <sfr@canb.auug.org.au> | 2008-08-26 16:19:09 +1000 |
---|---|---|
committer | Stephen Rothwell <sfr@canb.auug.org.au> | 2008-08-26 16:19:09 +1000 |
commit | faa48fc0772e62c190d28706d8c3edb8a9292e7f (patch) | |
tree | e91b3fbff2b7e68424c1e5dd1f6b9e83873c992c /lib/Kconfig.debug | |
parent | 4a8f9bb524796ecd1dc8d0ce0be2737c9bcbd249 (diff) | |
parent | 148db298f8201355eefb70bb34ae0b4d9dcd4bf2 (diff) |
Merge commit 'slab/for-next'
Diffstat (limited to 'lib/Kconfig.debug')
-rw-r--r-- | lib/Kconfig.debug | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index f62c706887c5..a34dc83c2b4e 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug @@ -675,6 +675,34 @@ 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. + +config KMEMTRACE_DEFAULT_ENABLED + bool "Enabled by default at boot" + depends on KMEMTRACE + help + Say Y here to enable kmemtrace at boot-time by default. Whatever + the choice, the behavior can be overridden by a kernel parameter, + as described in documentation. + menuconfig BUILD_DOCSRC bool "Build targets in Documentation/ tree" depends on HEADERS_CHECK |