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 <[email protected]>
>
> 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 ;)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
