From: Yuyang Du <yuyang.du@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
mingo@kernel.org, linux-kernel@vger.kernel.org, pjt@google.com,
dietmar.eggemann@arm.com, bsegall@google.com,
Morten.Rasmussen@arm.com
Subject: Re: [RFC PATCH v2] sched: reflect sched_entity movement into task_group's utilization
Date: Mon, 6 Jun 2016 07:58:54 +0800 [thread overview]
Message-ID: <20160605235854.GC8105@intel.com> (raw)
In-Reply-To: <20160601125407.GA28447@twins.programming.kicks-ass.net>
On Wed, Jun 01, 2016 at 02:54:07PM +0200, Peter Zijlstra wrote:
> On Tue, May 24, 2016 at 10:57:32AM +0200, Vincent Guittot wrote:
> > Ensure that the changes of the utilization of a sched_entity will be
> > reflected in the task_group hierarchy.
> >
> > This patch tries another way than the flat utilization hierarchy proposal
> > to ensure the changes will be propagated down to the root cfs.
>
> Which would be:
>
> lkml.kernel.org/r/1460327765-18024-5-git-send-email-yuyang.du@intel.com
>
> Right? Yuyang, there were some issues with the patches leading up to
> that proposal, were you going to update the flat util thing without
> those patches or can you find yourself in Vince's patches?
Sure. I am rebasing my proposal patches, will send out later.
> (just so I can get a picture of what all patches to look at when
> reviewing)
next prev parent reply other threads:[~2016-06-06 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 8:57 [RFC PATCH v2] sched: reflect sched_entity movement into task_group's utilization Vincent Guittot
2016-05-24 9:55 ` Vincent Guittot
2016-06-06 10:52 ` Dietmar Eggemann
2016-06-06 12:44 ` Vincent Guittot
2016-06-01 12:54 ` Peter Zijlstra
2016-06-01 19:45 ` Dietmar Eggemann
2016-06-05 23:58 ` Yuyang Du [this message]
2016-06-01 13:36 ` Peter Zijlstra
2016-06-01 15:26 ` Vincent Guittot
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=20160605235854.GC8105@intel.com \
--to=yuyang.du@intel.com \
--cc=Morten.Rasmussen@arm.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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 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.