[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20131210144744.GN3694@twins.programming.kicks-ass.net>
Date: Tue, 10 Dec 2013 15:47:44 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Eliezer Tamir <eliezer.tamir@...ux.intel.com>
Cc: John Stultz <john.stultz@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...e.hu>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Andy Lutomirski <luto@...capital.net>,
linux-kernel@...r.kernel.org, Tony Luck <tony.luck@...il.com>,
hpa@...or.com
Subject: Re: [RFC][PATCH 0/7] sched: Optimize sched_clock bits
On Tue, Dec 03, 2013 at 04:10:53PM +0100, Peter Zijlstra wrote:
> Also, static_key and related APIs suck donkey ballz -- I did indeed
> promise myself I'd not step into that bike shed contest but having had
> to use them again *painfull*.
> POST:
>
> [ 5.061000] sched_clock_stable: 1
> [ 18.916000] (cold) sched_clock: 1335206
> [ 32.576000] (cold) local_clock: 1365236
> [ 32.580000] (warm) sched_clock: 11771
> [ 32.584000] (warm) local_clock: 14725
It looks like this was using the jiffies (tsc_disabled) instead of rdtsc path.
/me curses static_key and co more.
--
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