From: Peter Zijlstra <peterz@infradead.org>
To: Andrew Hunter <ahh@google.com>
Cc: pavankumar kondeti <pavankumar.kondeti@gmail.com>,
Pavan Kondeti <pkondeti@codeaurora.org>,
lkml <linux-kernel@vger.kernel.org>,
Mike Galbraith <umgwanakikbuti@gmail.com>,
Ingo Molnar <mingo@kernel.org>, Paul Turner <pjt@google.com>,
Ben Segall <bsegall@google.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Morten Rasmussen <morten.rasmussen@arm.com>,
byungchul.park@lge.com
Subject: Re: Migrated CFS task getting an unfair advantage
Date: Wed, 9 Mar 2016 20:21:17 +0100 [thread overview]
Message-ID: <20160309192117.GN6344@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CADroS=6Ncpao6WWXBxboB6quqUP96EnjbsDUZqNgASd_PzDGaA@mail.gmail.com>
On Wed, Mar 09, 2016 at 11:00:42AM -0800, Andrew Hunter wrote:
> At Google, we essentially reverted 88ec22d and the subsequent tweaks
> to it, keeping vruntime absolute always , instead using
> task_move_group_fair to change the basis of relative min_vruntime
> between cpus. We found this made it a lot easier to reason about and
> work with corss-cpu computations. I could post the patch if it would
> be of interest...
Yes please, Paul said he would many times.
next prev parent reply other threads:[~2016-03-09 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 9:22 Migrated CFS task getting an unfair advantage Pavan Kondeti
2016-03-09 12:04 ` Peter Zijlstra
2016-03-09 13:06 ` pavankumar kondeti
2016-03-09 19:00 ` Andrew Hunter
2016-03-09 19:21 ` Peter Zijlstra [this message]
2016-03-09 23:48 ` Byungchul Park
2016-05-09 15:28 ` Peter Zijlstra
2016-03-21 11:16 ` [tip:sched/urgent] sched/fair: Fix fairness issue on migration tip-bot for Peter Zijlstra
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=20160309192117.GN6344@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ahh@google.com \
--cc=bsegall@google.com \
--cc=byungchul.park@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=pavankumar.kondeti@gmail.com \
--cc=pjt@google.com \
--cc=pkondeti@codeaurora.org \
--cc=umgwanakikbuti@gmail.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