From: Peter Zijlstra <peterz@infradead.org>
To: Norbert Preining <preining@logic.at>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
akpm <akpm@linux-foundation.org>, Mike Galbraith <efault@gmx.de>,
tglx <tglx@linutronix.de>
Subject: Re: high power consumption in recent kernels
Date: Thu, 08 Jul 2010 17:59:39 +0200 [thread overview]
Message-ID: <1278604779.1900.157.camel@laptop> (raw)
In-Reply-To: <1278595426.1900.130.camel@laptop>
On Thu, 2010-07-08 at 15:23 +0200, Peter Zijlstra wrote:
> On Thu, 2010-07-08 at 21:46 +0900, Norbert Preining wrote:
> > Looks promising, reverting the old patch, adding that one, building,
> > running, unplugging ppower, powertop runs now since some time,
> > it seems that we are back to better situation:
>
> Hrmm, Mike seems you wrecked power usage..
>
> So nohz_ratelimit() prevents us from entering NOHZ when the last attempt
> was less than 1/2 a jiffy ago (fwiw: NSEC_PER_SEC/HZ == TICK_NSEC).
>
> Its either entering idle or irq_exit trying to enter nohz state, if we
> keep skipping it it means that we get enough interrupt activity to
> render nohz useless anyway.. so not quite sure how this wrecks things..
OK, so Arjan said the gain could come from tricking the idle governor
into not using deeper C states. He also said he significantly cured said
governor in .35.
Mike could you re-run your netperf tests that showed the 10% throughput
gain? Hopefully the fixed governor will yield the same result and we can
kill off this ratelimit thing.
next prev parent reply other threads:[~2010-07-08 15:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 16:45 high power consumption in recent kernels Norbert Preining
2010-07-08 9:06 ` Peter Zijlstra
2010-07-08 11:57 ` Arjan van de Ven
2010-07-08 11:58 ` Peter Zijlstra
2010-07-08 12:04 ` Norbert Preining
2010-07-08 12:22 ` Peter Zijlstra
2010-07-08 12:46 ` Norbert Preining
2010-07-08 13:23 ` Peter Zijlstra
2010-07-08 15:59 ` Peter Zijlstra [this message]
2010-07-08 19:06 ` Peter Zijlstra
2010-07-08 19:40 ` Mike Galbraith
2010-07-08 20:44 ` Peter Zijlstra
2010-07-09 3:08 ` Arjan van de Ven
2010-07-09 5:55 ` Mike Galbraith
2010-07-08 19:37 ` Mike Galbraith
2010-07-08 15:11 ` Arjan van de Ven
2010-07-09 19:09 ` Pavel Machek
[not found] <1283840425.26157.6486.camel@debian>
[not found] ` <20100909093140.GC29648@gamma.logic.tuwien.ac.at>
[not found] ` <EA929A9653AAE14F841771FB1DE5A1366008738EC2@rrsmsx501.amr.corp.intel.com>
[not found] ` <20100909205115.GD11053@gamma.logic.tuwien.ac.at>
[not found] ` <1284107099.402.30.camel@laptop>
2010-09-10 14:48 ` Shi, Alex
2010-09-10 14:54 ` Norbert Preining
2010-09-13 5:21 ` Alex,Shi
2010-09-17 2:09 ` Alex,Shi
2010-09-22 15:44 ` Norbert Preining
2010-09-28 10:40 ` Alex,Shi
2010-09-29 14:39 ` Norbert Preining
2010-09-29 15:48 ` Chen, Tim C
2010-09-30 0:50 ` Alex,Shi
2010-09-30 2:01 ` Norbert Preining
2010-09-30 6:59 ` Norbert Preining
2010-09-30 8:27 ` Alex,Shi
2010-09-30 12:36 ` Peter Zijlstra
2010-09-30 13:21 ` Shi, Alex
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=1278604779.1900.157.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=preining@logic.at \
--cc=tglx@linutronix.de \
/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