[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090114202736.GB6519@elte.hu>
Date: Wed, 14 Jan 2009 21:27:36 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
torvalds@...ux-foundation.org, paulmck@...ux.vnet.ibm.com,
ghaskins@...ell.com, matthew@....cx, andi@...stfloor.org,
chris.mason@...cle.com, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-btrfs@...r.kernel.org,
tglx@...utronix.de, npiggin@...e.de, pmorreale@...ell.com,
SDietrich@...ell.com, dmitry.adamushko@...il.com,
hannes@...xchg.org
Subject: Re: [GIT PULL] adaptive spinning mutexes
* Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> On Wed, 2009-01-14 at 11:36 -0800, Andrew Morton wrote:
>
> > Do people enable CONFIG_SCHED_DEBUG?
>
> Well, I have it always enabled, but I've honestly no idea if that makes
> me weird.
>
> > CONFIG_DEBUG_MUTEXES=n, CONFIG_SCHED_DEBUG=y is getting to be a pretty
> > small subset?
>
> Could be, do you fancy me doing a sysctl? shouldn't be hard.
i dunno, why another fancy sysctl for something that fits quite nicely
into the existing sched_features scheme that we've been using for such
purposes for the past 3-4 kernel releases?
we always provided various toggles for new scheduler features via
/sys/debug/sched_features, so that people can do performance regression
testing, and it works quite well.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists