From: Peter Zijlstra <peterz@infradead.org>
To: "Alex,Shi" <alex.shi@intel.com>
Cc: "ncrao@google.com" <ncrao@google.com>,
"mingo@elte.hu" <mingo@elte.hu>,
"Chen, Tim C" <tim.c.chen@intel.com>,
"Li, Shaohua" <shaohua.li@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
len.brown@intel.com
Subject: Re: power increase issue on light load
Date: Tue, 28 Jun 2011 16:59:40 +0200 [thread overview]
Message-ID: <1309273180.6701.213.camel@twins> (raw)
In-Reply-To: <1309219329.14604.11.camel@debian>
On Tue, 2011-06-28 at 08:02 +0800, Alex,Shi wrote:
> > >
> > > What happens if you try something like the below. Increased imbalance
> > > might lead to more load-balance action, which might lead to more task
> > > migration/waking up of cpus etc.
> > >
> > > If the below makes any difference, Nikhil's changes have a funny that
> > > needs to be caught.
> >
> > Yes, it most remove the commit effect, So the power recovered.
> >
> > In fact the only suspicious I found is large imbalance, but that is
> > the commit want ...
>
> Any further comments for this?
I had a look over all that stuff, but I couldn't find an obvious unit
mis-match in any of the imbalance code. Nikhil any clue?
next prev parent reply other threads:[~2011-06-28 15:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 2:43 power increase issue on light load Alex,Shi
2011-06-23 9:02 ` Peter Zijlstra
2011-06-24 0:41 ` Alex,Shi
2011-06-28 0:02 ` Alex,Shi
2011-06-28 14:59 ` Peter Zijlstra [this message]
2011-06-28 17:13 ` Nikhil Rao
2011-06-29 2:30 ` Nikhil Rao
2011-06-29 3:22 ` Alex,Shi
2011-06-29 6:55 ` Alex,Shi
2011-06-30 0:26 ` Nikhil Rao
2011-06-30 8:38 ` Alex,Shi
2011-06-30 0:07 ` Nikhil Rao
2011-06-30 8:34 ` Alex,Shi
2011-07-01 5:44 ` Ming Lei
2011-07-01 18:00 ` Nikhil Rao
2011-07-01 23:51 ` Ming Lei
2011-07-04 0:45 ` Alex,Shi
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=1309273180.6701.213.camel@twins \
--to=peterz@infradead.org \
--cc=alex.shi@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ncrao@google.com \
--cc=shaohua.li@intel.com \
--cc=tim.c.chen@intel.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.