diff options
| author | Tim Chen <tim.c.chen@linux.intel.com> | 2006-04-18 22:21:47 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-04-19 09:13:51 -0700 |
| commit | cca57c5b5ab164e3c96576fc7739c0a30c2eab72 (patch) | |
| tree | 24a41ba1348d12f25c9e0da3b9b7cbaf4f1ce891 | |
| parent | ca99c1da080345e227cfb083c330a184d42e27f3 (diff) | |
| download | linux-3.10-cca57c5b5ab164e3c96576fc7739c0a30c2eab72.tar.gz linux-3.10-cca57c5b5ab164e3c96576fc7739c0a30c2eab72.tar.bz2 linux-3.10-cca57c5b5ab164e3c96576fc7739c0a30c2eab72.zip | |
[PATCH] Kconfig.debug: Set DEBUG_MUTEX to off by default
DEBUG_MUTEX flag is on by default in current kernel configuration.
During performance testing, we saw mutex debug functions like
mutex_debug_check_no_locks_freed (called by kfree()) is expensive as it
goes through a global list of memory areas with mutex lock and do the
checking. For benchmarks such as Volanomark and Hackbench, we have seen
more than 40% drop in performance on some platforms. We suggest to set
DEBUG_MUTEX off by default. Or at least do that later when we feel that
the mutex changes in the current code have stabilized.
Signed-off-by: Tim Chen <tim.c.chen@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
| -rw-r--r-- | lib/Kconfig.debug | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index d57fd9181b1..6ecc180beb7 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug @@ -101,7 +101,7 @@ config DEBUG_PREEMPT config DEBUG_MUTEXES bool "Mutex debugging, deadlock detection" - default y + default n depends on DEBUG_KERNEL help This allows mutex semantics violations and mutex related deadlocks |