All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@google.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH] Default CONFIG_DEBUG_MUTEXES to n
Date: Sat, 15 Apr 2006 15:45:38 -0700	[thread overview]
Message-ID: <44417792.2070900@google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 194 bytes --]

CONFIG_DEBUG_MUTEXES has a significant performant impact (reduced perf
of reaim by 50% on ia32 NUMA boxes). It should not be on by default.

Signed-off-by: Martin J. Bligh <mbligh@google.com>



[-- Attachment #2: 2.6.17-rc1_no_mutex_dbg --]
[-- Type: text/plain, Size: 722 bytes --]

diff -aurpN -X /home/mbligh/.diff.exclude linux-2.6.17-rc1/lib/Kconfig.debug 2.6.17-rc1_no_mutex_dbg/lib/Kconfig.debug
--- linux-2.6.17-rc1/lib/Kconfig.debug	2006-04-15 15:28:54.000000000 -0700
+++ 2.6.17-rc1_no_mutex_dbg/lib/Kconfig.debug	2006-04-15 15:44:14.000000000 -0700
@@ -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
@@ -109,6 +109,7 @@ config DEBUG_MUTEXES
 
 config DEBUG_SPINLOCK
 	bool "Spinlock debugging"
+	default n
 	depends on DEBUG_KERNEL
 	help
 	  Say Y here and build SMP to catch missing spinlock initialization

             reply	other threads:[~2006-04-15 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-15 22:45 Martin J. Bligh [this message]
2006-04-15 23:06 ` [PATCH] Default CONFIG_DEBUG_MUTEXES to n Adrian Bunk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44417792.2070900@google.com \
    --to=mbligh@google.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.