From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <efault@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes
Date: Fri, 7 Oct 2016 16:22:24 -0400 [thread overview]
Message-ID: <57F80400.9040503@canonical.com> (raw)
In-Reply-To: <CA+55aFw5DTubaqgszpZW44gnt_k-_1ENjgrtWo6M9hexbbJsBw@mail.gmail.com>
On 10/07/2016 03:57 PM, Linus Torvalds wrote:
> On Fri, Oct 7, 2016 at 12:38 PM, Joseph Salisbury
> <joseph.salisbury@canonical.com> wrote:
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit resolved this bug:
> Hmm. Interesting, and it sounds like we should revert that unless
> somebody figures out *why* following the rules wrt cfq updates causes
> problems. But I also wonder what the Ubuntu kernel config is. Does
> Ubuntu enable CONFIG_SCHED_AUTOGROUP=y, for example? Because
> regardless of any other scheduler issues, autogrouping *should* mean
> that when you run some CPU hogger in one session, that should still
> balance all CPU time with other sessions..
>
> I'm not seeing anything odd on my xps13, which should have a similar
> CPU to the X1 Carbon.
>
> Linus
Hi Linus,
Yes, CONFIG_SCHED_AUTOGROUP is enabled in the Ubuntu kernel. However,
that config was also enable in the Ubuntu 4.4 kerrnels without seeing
this issue. I can try disabling the config in the 4.8 based kernel and
see if that changes things.
Thanks,
Joe
next prev parent reply other threads:[~2016-10-07 20:22 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 19:38 Joseph Salisbury
2016-10-07 19:57 ` Linus Torvalds
2016-10-07 20:22 ` Joseph Salisbury [this message]
2016-10-07 20:37 ` Linus Torvalds
2016-10-08 8:00 ` Peter Zijlstra
2016-10-08 8:39 ` Ingo Molnar
2016-10-08 11:37 ` Vincent Guittot
2016-10-08 11:49 ` Mike Galbraith
2016-10-12 12:20 ` Vincent Guittot
2016-10-12 15:35 ` Joseph Salisbury
2016-10-12 16:21 ` Joseph Salisbury
2016-10-13 10:58 ` Vincent Guittot
2016-10-13 15:52 ` Joseph Salisbury
2016-10-13 16:48 ` Vincent Guittot
2016-10-13 18:49 ` Dietmar Eggemann
2016-10-13 21:34 ` Vincent Guittot
2016-10-14 8:24 ` Vincent Guittot
2016-10-14 13:10 ` Dietmar Eggemann
2016-10-14 15:18 ` Vincent Guittot
2016-10-14 16:04 ` Joseph Salisbury
2016-10-17 9:09 ` Vincent Guittot
2016-10-17 11:49 ` Dietmar Eggemann
2016-10-17 13:19 ` Peter Zijlstra
2016-10-17 13:54 ` Vincent Guittot
2016-10-17 22:52 ` Dietmar Eggemann
2016-10-18 8:43 ` Vincent Guittot
2016-10-18 9:07 ` Peter Zijlstra
2016-10-18 9:45 ` Vincent Guittot
2016-10-18 10:34 ` Peter Zijlstra
2016-10-18 11:56 ` Vincent Guittot
2016-10-18 21:58 ` Joonwoo Park
2016-10-19 6:42 ` Vincent Guittot
2016-10-19 9:46 ` Dietmar Eggemann
2016-10-19 11:25 ` Vincent Guittot
2016-10-19 15:33 ` Dietmar Eggemann
2016-10-19 17:33 ` Joonwoo Park
2016-10-19 17:50 ` Vincent Guittot
2016-10-19 11:33 ` Peter Zijlstra
2016-10-19 11:50 ` Vincent Guittot
2016-10-19 13:30 ` Morten Rasmussen
2016-10-19 17:41 ` Vincent Guittot
2016-10-20 7:56 ` Morten Rasmussen
2016-10-19 14:49 ` Joseph Salisbury
2016-10-19 14:53 ` Vincent Guittot
2016-10-18 11:15 ` Dietmar Eggemann
2016-10-18 12:07 ` 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=57F80400.9040503@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome