From: Peter Zijlstra <peterz@infradead.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Yuyang Du <yuyang.du@intel.com>, Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
vincent.guittot@linaro.org, Morten.Rasmussen@arm.com,
dietmar.eggemann@arm.com, pjt@google.com, bsegall@google.com
Subject: Re: group scheduler regression since 4.3 (bisect 9d89c257d sched/fair: Rewrite runnable load and utilization average tracking)
Date: Mon, 26 Sep 2016 13:53:00 +0200 [thread overview]
Message-ID: <20160926115300.GA5016@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <f7257223-10d3-f453-a7b8-a10f9bb7f537@de.ibm.com>
On Mon, Sep 26, 2016 at 01:42:05PM +0200, Christian Borntraeger wrote:
> On 09/26/2016 12:56 PM, Peter Zijlstra wrote:
> > One of the differences in the old and new thing is being addressed by
> > these patches:
> >
> > https://lkml.kernel.org/r/1473666472-13749-1-git-send-email-vincent.guittot@linaro.org
> >
> > Could you see if those patches make a difference? If not, we'll have to
> > go poke elsewhere ofcourse ;-)
>
> Those patches do not apply cleanly on v4.7, linux/master or next/master.
> Is there a good branch to test these patches?
They seemed to apply for me on tip/sched/core, I pushed out a branch for
you that has them on.
git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git sched/propagate
I didn't boot the result though; but they applied without issue.
next prev parent reply other threads:[~2016-09-26 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 10:42 group scheduler regression since 4.3 (bisect 9d89c257d sched/fair: Rewrite runnable load and utilization average tracking) Christian Borntraeger
2016-09-26 10:56 ` Peter Zijlstra
2016-09-26 11:42 ` Christian Borntraeger
2016-09-26 11:53 ` Peter Zijlstra [this message]
2016-09-26 12:01 ` Christian Borntraeger
2016-09-26 12:10 ` Peter Zijlstra
2016-09-26 12:49 ` Christian Borntraeger
2016-09-26 14:12 ` Christian Borntraeger
2016-09-26 12:25 ` 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=20160926115300.GA5016@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Morten.Rasmussen@arm.com \
--cc=borntraeger@de.ibm.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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 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.