From: Frederic Weisbecker <fweisbec@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Alessio Igor Bogani <abogani@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Metcalf <cmetcalf@tilera.com>,
Geoff Levand <geoff@infradead.org>,
Gilad Ben Yossef <gilad@benyossef.com>,
Hakan Akkan <hakanakkan@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Li Zhong <zhong@linux.vnet.ibm.com>,
Namhyung Kim <namhyung.kim@lge.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.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: Fri, 8 Feb 2013 16:53:17 +0100 [thread overview]
Message-ID: <CAFTL4hyfnhjezjL2QfVKYDB-bwh4BSGyX8xmhpdmxTf+EAu+yA@mail.gmail.com> (raw)
In-Reply-To: <0000013cb614e4e5-10f6e9ce-08e1-47f6-9044-565b4084c354-000000@email.amazonses.com>
2013/2/7 Christoph Lameter <cl@linux.com>:
> On Thu, 7 Feb 2013, Frederic Weisbecker wrote:
>
>> Not with hrtick.
>
> hrtick? Did we not already try that a couple of years back and it turned
> out that the overhead of constantly reprogramming a timer via the PCI bus
> was causing too much of a performance regression?
Yeah Peter said that especially reprogramming the clock everytime we
call schedule() was killing the performances. Now may be on some
workloads, with the tick stopped, we can find some new results.
next prev parent reply other threads:[~2013-02-08 15:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 18:28 [ANNOUNCE] 3.8-rc6-nohz4 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
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 [this message]
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=CAFTL4hyfnhjezjL2QfVKYDB-bwh4BSGyX8xmhpdmxTf+EAu+yA@mail.gmail.com \
--to=fweisbec@gmail.com \
--cc=abogani@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=cmetcalf@tilera.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=paulmck@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.