[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52ea5cf6-b22b-f026-5796-f52b3e40415a@google.com>
Date: Fri, 31 Aug 2018 15:24:04 -0700
From: Steve Muckle <smuckle@...gle.com>
To: Dietmar Eggemann <dietmar.eggemann@....com>,
Peter Zijlstra <peterz@...radead.org>
Cc: Miguel de Dios <migueldedios@...gle.com>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
kernel-team@...roid.com, Todd Kjos <tkjos@...gle.com>,
Paul Turner <pjt@...gle.com>,
Quentin Perret <quentin.perret@....com>,
Patrick Bellasi <Patrick.Bellasi@....com>,
Chris Redpath <Chris.Redpath@....com>,
Morten Rasmussen <Morten.Rasmussen@....com>,
John Dias <joaodias@...gle.com>
Subject: Re: [PATCH] sched/fair: vruntime should normalize when switching from
fair
On 08/29/2018 08:33 AM, Dietmar Eggemann wrote:
> Yes, this solves the issue for the case I described. Using
> 'p->sched_remote_wakeup' (WF_MIGRATED) looks more elegant than using
> 'p->sched_class == &fair_sched_class'.
It's confirmed that this patch solves the original issue we saw (and my
test case passes for me as well). I will send this version out shortly.
Powered by blists - more mailing lists