From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org, pjt@google.com,
yuyang.du@intel.com, bsegall@google.com,
Morten.Rasmussen@arm.com
Subject: Re: [RFC PATCH v2] sched: reflect sched_entity movement into task_group's utilization
Date: Wed, 1 Jun 2016 20:45:27 +0100 [thread overview]
Message-ID: <574F3B57.50801@arm.com> (raw)
In-Reply-To: <20160601125407.GA28447@twins.programming.kicks-ass.net>
On 01/06/16 13:54, 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.
IMHO, the 'flat utilization hierarchy' discussion started here:
https://lkml.org/lkml/2016/4/1/514
In the meantime I continued to play with the idea of a flat utilization
hierarchy based on the exiting PELT code. I just sent out the RFC patch
set for people to compare with Vincent's approach.
> 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?
I think Yuyang dropped the 'flat utilization hierarchy' in
https://lkml.org/lkml/2016/4/28/270
> (just so I can get a picture of what all patches to look at when
> reviewing)
next prev parent reply other threads:[~2016-06-01 19:45 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 [this message]
2016-06-05 23:58 ` Yuyang Du
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=574F3B57.50801@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=Morten.Rasmussen@arm.com \
--cc=bsegall@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=vincent.guittot@linaro.org \
--cc=yuyang.du@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox