From: Yuyang Du <yuyang.du@intel.com>
To: Ingo Molnar <mingo@kernel.org>, peterz@infradead.org
Cc: peterz@infradead.org, linux-kernel@vger.kernel.org,
pjt@google.com, bsegall@google.com, morten.rasmussen@arm.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
lizefan@huawei.com
Subject: Re: [PATCH 1/4] sched/fair: Generalize the load/util averages resolution definition
Date: Sat, 10 Oct 2015 07:04:15 +0800 [thread overview]
Message-ID: <20151009230415.GI11102@intel.com> (raw)
In-Reply-To: <20151006080000.GH11102@intel.com>
On Tue, Oct 06, 2015 at 04:00:00PM +0800, Yuyang Du wrote:
> On Mon, Oct 05, 2015 at 09:04:45AM +0200, Ingo Molnar wrote:
> >
> > * Yuyang Du <yuyang.du@intel.com> wrote:
> >
> > > +# define SCHED_RESOLUTION_SHIFT 10
> >
> > > #if 0 /* BITS_PER_LONG > 32 -- currently broken: it increases power usage under light load */
> >
> > Might be worth fixing?
>
> Yes, it should be. Peter has already brought this up.
Do you have any suggestion on how to fix this?
Thanks,
Yuyang
next prev parent reply other threads:[~2015-10-10 6:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 17:56 [PATCH 0/4] sched/fair: Clean up sched metric definitions Yuyang Du
2015-10-04 17:56 ` [PATCH 1/4] sched/fair: Generalize the load/util averages resolution definition Yuyang Du
2015-10-05 7:04 ` Ingo Molnar
2015-10-06 8:00 ` Yuyang Du
2015-10-09 23:04 ` Yuyang Du [this message]
2015-10-05 10:52 ` Peter Zijlstra
2015-10-04 17:56 ` [PATCH 2/4] sched/fair: Remove SCHED_LOAD_SHIFT and SCHED_LOAD_SCALE Yuyang Du
2015-10-06 9:29 ` Vincent Guittot
2015-10-04 17:56 ` [PATCH 3/4] sched/fair: Remove scale_load_down() for load_avg Yuyang Du
2015-10-04 17:56 ` [PATCH 4/4] sched/fair: Rename scale_load() and scale_load_down() Yuyang Du
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=20151009230415.GI11102@intel.com \
--to=yuyang.du@intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=vincent.guittot@linaro.org \
/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).