Cc: <linux-kernel@...>, Con Kolivas <kernel@...>, Derek L. Fults <dfults@...>, devik <devik@...>, Dinakar Guniguntala <dino@...>, Emmanuel Pacaud <emmanuel.pacaud@...>, Frederik Deweerdt <deweerdt@...>, Ingo Molnar <mingo@...>, Matthew Dobson <colpatch@...>, Max Krasnyansky <maxk@...>, Nick Piggin <nickpiggin@...>, <rostedt@...>, Oleg Nesterov <oleg@...>, Paul E. McKenney <paulmck@...>, Paul Menage <menage@...>, Peter Zijlstra <a.p.zijlstra@...>, Randy.Dunlap <rddunlap@...>, <suresh.b.siddha@...>, Thomas Gleixner <tglx@...>
Paul,
On Sun, Jun 01, 2008 at 09:30:19PM -0500, Paul Jackson wrote:
We use it.
We use isolcpus to ensure that boot-time intialization, specifically timer initialization, happens on a specific set of cpus that we won't be using for lower latency purposes. Some of these timers will repeatedly restart themselves on the same cpu and a few do add latency (although admittedly I haven't checked timer latency recently).
Looking at tracebacks in 2.6.26-rc3 from hrtimer_init() and internal_add_timer() things still appear to be working this way, with the timer starting on the originating cpu. If I isolate all but, say one, cpu, timers all seem to start on the unisolated cpu.
Attempts have been made to add an interface to ward timers off of specific cpus, but these have always been rejected.
Why?
A better idea than just removing it.
--
