From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 1/3] ia64: enable CONFIG_DEBUG_SPINLOCK_SLEEP
Date: Wed, 20 Dec 2006 09:46:40 +0000 [thread overview]
Message-ID: <45890680.5050001@sgi.com> (raw)
In-Reply-To: <200612192104.kBJL4gfn010370@shell0.pdx.osdl.net>
Andrew Morton wrote:
>> Please don't do this in the sn2 defconfig! Spin lock debugging totally
>> kills scalability. I'll end up with a ton of internal complaints over
>> the kernel not performing if this goes in :-(
>
> Well you tell me how to stop ia64 developers from submitting stuff which
> has stupid bugs which instamanifest for everyone else? It is not uncommon.
Beat them with a stick?
Seriously, not sure how to deal with it. I try and keep the
sn2_defconfig to match the actual hardware and my colleagues rely on
being able to build that. With spin lock debugging enabled we can barely
boot the system on medium to large boxes.
If you get stuff like that from someone with an sgi.com address, let me
know and I'll apply the clue 2x4.
Cheers,
Jes
next prev parent reply other threads:[~2006-12-20 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 21:04 [patch 1/3] ia64: enable CONFIG_DEBUG_SPINLOCK_SLEEP akpm
2006-12-20 9:27 ` Jes Sorensen
2006-12-20 9:38 ` Andrew Morton
2006-12-20 9:46 ` Jes Sorensen [this message]
2006-12-20 9:53 ` Andrew Morton
2006-12-20 9:56 ` Jes Sorensen
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=45890680.5050001@sgi.com \
--to=jes@sgi.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox