From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Alessio Igor Bogani <abogani@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Metcalf <cmetcalf@tilera.com>,
Christoph Lameter <cl@linux.com>,
Geoff Levand <geoff@infradead.org>,
Gilad Ben Yossef <gilad@benyossef.com>,
Hakan Akkan <hakanakkan@gmail.com>,
Li Zhong <zhong@linux.vnet.ibm.com>,
Namhyung Kim <namhyung.kim@lge.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [ANNOUNCE] 3.8-rc6-nohz4
Date: Thu, 7 Feb 2013 09:37:56 -0800 [thread overview]
Message-ID: <20130207173756.GW2632@linux.vnet.ibm.com> (raw)
In-Reply-To: <1360256781.2621.80.camel@gandalf.local.home>
On Thu, Feb 07, 2013 at 12:06:21PM -0500, Steven Rostedt wrote:
> 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.
As long as we don't end up replacing a single tick with multiple hrtimers
(or whatever), ending up with more overhead and disruption than we
started with. ;-)
Thanx, Paul
next prev parent reply other threads:[~2013-02-07 17:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 18:28 Frederic Weisbecker
2013-02-07 2:50 ` Steven Rostedt
2013-02-07 11:10 ` Ingo Molnar
2013-02-07 15:41 ` Christoph Lameter
2013-02-07 16:12 ` Steven Rostedt
2013-02-07 16:30 ` Paul E. McKenney
2013-02-07 17:06 ` Steven Rostedt
2013-02-07 17:37 ` Paul E. McKenney [this message]
2013-02-07 16:25 ` Frederic Weisbecker
2013-02-07 16:41 ` Steven Rostedt
2013-02-07 16:45 ` Frederic Weisbecker
2013-02-07 17:03 ` Steven Rostedt
2013-02-07 17:45 ` Frederic Weisbecker
2013-02-07 19:07 ` Ingo Molnar
2013-02-07 19:19 ` Steven Rostedt
2013-02-08 15:51 ` Frederic Weisbecker
2013-02-11 9:59 ` Ingo Molnar
2013-02-07 16:41 ` Frederic Weisbecker
2013-02-07 17:00 ` Steven Rostedt
2013-02-07 17:18 ` Frederic Weisbecker
2013-02-07 19:14 ` Christoph Lameter
2013-02-07 19:55 ` Ingo Molnar
2013-02-08 6:18 ` Mike Galbraith
2013-02-08 15:53 ` Frederic Weisbecker
2013-02-08 16:18 ` Steven Rostedt
2013-02-08 16:24 ` Christoph Lameter
2013-02-08 18:57 ` Clark Williams
2013-02-08 19:43 ` Christoph Lameter
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=20130207173756.GW2632@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=abogani@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=cmetcalf@tilera.com \
--cc=fweisbec@gmail.com \
--cc=geoff@infradead.org \
--cc=gilad@benyossef.com \
--cc=hakanakkan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=zhong@linux.vnet.ibm.com \
/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
Powered by JetHome