[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1360256781.2621.80.camel@gandalf.local.home>
Date: Thu, 07 Feb 2013 12:06:21 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: paulmck@...ux.vnet.ibm.com
Cc: Ingo Molnar <mingo@...nel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Alessio Igor Bogani <abogani@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Chris Metcalf <cmetcalf@...era.com>,
Christoph Lameter <cl@...ux.com>,
Geoff Levand <geoff@...radead.org>,
Gilad Ben Yossef <gilad@...yossef.com>,
Hakan Akkan <hakanakkan@...il.com>,
Li Zhong <zhong@...ux.vnet.ibm.com>,
Namhyung Kim <namhyung.kim@....com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [ANNOUNCE] 3.8-rc6-nohz4
On Thu, 2013-02-07 at 08:30 -0800, Paul E. McKenney wrote:
> I suspect that removal of jiffies from the kernel will take a few stages,
> with RCU being one of the laggards for awhile. Making RCU's state
> machine depend wholly on process-based execution will take some care
> and experimentation, especially for extreme and corner-case workloads.
> For example, having RCU OOM the system just because a specific CPU was
> unable to run some RCU kthread for an extended time is something to
> be avoided. ;-)
Tickless doesn't mean no timeouts or periodic timers. I think we will
always have some sort of dynamic tick when needed. It will just be more
event driven then something that goes off constantly.
-- Steve
--
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