* [PATCH] Kconfig.debug: Set DEBUG_MUTEX to off by default
@ 2006-04-07 16:56 Tim Chen
2006-04-08 14:42 ` Arjan van de Ven
0 siblings, 1 reply; 2+ messages in thread
From: Tim Chen @ 2006-04-07 16:56 UTC (permalink / raw)
To: linux-kernel
Hi,
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.
Tim Chen
Signed-off-by: Tim Chen <tim.c.chen@intel.com>
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
--- 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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] Kconfig.debug: Set DEBUG_MUTEX to off by default
2006-04-07 16:56 [PATCH] Kconfig.debug: Set DEBUG_MUTEX to off by default Tim Chen
@ 2006-04-08 14:42 ` Arjan van de Ven
0 siblings, 0 replies; 2+ messages in thread
From: Arjan van de Ven @ 2006-04-08 14:42 UTC (permalink / raw)
To: tim.c.chen; +Cc: linux-kernel
On Fri, 2006-04-07 at 09:56 -0700, Tim Chen wrote:
> Hi,
>
> 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.
>
> Tim Chen
>
> Signed-off-by: Tim Chen <tim.c.chen@intel.com>
>
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> --- 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
don't do default n, just remove the line instead ;)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-04-08 14:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-04-07 16:56 [PATCH] Kconfig.debug: Set DEBUG_MUTEX to off by default Tim Chen
2006-04-08 14:42 ` Arjan van de Ven
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®