From: Arjan van de Ven <arjan@linux.intel.com>
To: paulmck@linux.vnet.ibm.com
Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>,
Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
Len Brown <len.brown@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Zhang Rui <rui.zhang@intel.com>, Rob Landley <rob@landley.net>
Subject: Re: [PATCH 3/3] PM: Introduce Intel PowerClamp Driver
Date: Tue, 13 Nov 2012 18:59:06 -0800 [thread overview]
Message-ID: <50A308FA.40001@linux.intel.com> (raw)
In-Reply-To: <20121114013459.GS2489@linux.vnet.ibm.com>
On 11/13/2012 5:34 PM, Paul E. McKenney wrote:
> On Tue, Nov 13, 2012 at 05:14:50PM -0800, Jacob Pan wrote:
>> On Tue, 13 Nov 2012 16:08:54 -0800
>> Arjan van de Ven <arjan@linux.intel.com> wrote:
>>
>>>> I think I know, but I feel the need to ask anyway. Why not tell
>>>> RCU about the clamping?
>>>
>>> I don't mind telling RCU, but what cannot happen is a bunch of CPU
>>> time suddenly getting used (since that is the opposite of what is
>>> needed at the specific point in time of going idle)
>
> Another round of RCU_FAST_NO_HZ rework, you are asking for? ;-)
well
we can tell you we're about to mwait
and we can tell you when we're done being idle.
you could just do the actual work at that point, we don't care anymore ;-)
just at the start of the mandated idle period we can't afford to have more
jitter than we already have (which is more than I'd like, but it's manageable.
More jitter means more performance hit, since during the time of the jitter, some cpus
are forced idle, e.g. costing performance, without the actual big-step power savings
kicking in yet....)
> If you are only having the system take 6-millisecond "vacations", probably
it's not all that different from running a while (1) loop for 6 msec inside
a kernel thread.... other than the power level of course...
next prev parent reply other threads:[~2012-11-14 2:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 22:03 [PATCH 0/3] pm: Intel powerclamp driver Jacob Pan
2012-11-12 22:03 ` [PATCH 1/3] tick: export nohz tick idle symbols for module use Jacob Pan
2012-11-12 22:03 ` [PATCH 2/3] x86/nmi: export local_touch_nmi() symbol for modules Jacob Pan
2012-11-12 22:03 ` [PATCH 3/3] PM: Introduce Intel PowerClamp Driver Jacob Pan
2012-11-13 6:33 ` Joe Perches
2012-11-13 6:55 ` Jacob Pan
2012-11-13 21:16 ` Paul E. McKenney
2012-11-13 21:39 ` Jacob Pan
2012-11-13 22:23 ` Paul E. McKenney
2012-11-13 22:45 ` Arjan van de Ven
2012-11-13 23:02 ` Rafael J. Wysocki
2012-11-14 0:03 ` Paul E. McKenney
2012-11-14 0:03 ` Paul E. McKenney
2012-11-14 0:08 ` Arjan van de Ven
2012-11-14 1:14 ` Jacob Pan
2012-11-14 1:34 ` Paul E. McKenney
2012-11-14 2:59 ` Arjan van de Ven [this message]
2012-11-15 3:22 ` Paul E. McKenney
2012-11-14 1:24 ` Jacob Pan
2012-11-13 21:56 ` Arjan van de Ven
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=50A308FA.40001@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rob@landley.net \
--cc=rui.zhang@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).