Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Chiluk <chiluk+linux@indeed.com>
Cc: stable@vger.kernel.org
Subject: Re: Please backport de53fd7aedb1 : sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices
Date: Wed, 25 Sep 2019 08:44:14 +0200	[thread overview]
Message-ID: <20190925064414.GA1449297@kroah.com> (raw)
In-Reply-To: <CAC=E7cUXpUDgpvsmMaMU6sAydbfD0FEJiK25R1r=e9=YtcPjGw@mail.gmail.com>

On Wed, Sep 25, 2019 at 12:53:48AM -0500, Dave Chiluk wrote:
> Commit de53fd7aedb1 ("sched/fair: Fix low cpu usage with high
> throttling by removing expiration of cpu-local slices") fixes a major
> performance issue for containerized clouds such as Kubernetes.
> 
> Commit de53fd7aedb1 Fixes commit : 512ac999d275 ("sched/fair: Fix
> bandwidth timer clock drift condition").
> 
> This should be applied to all stable kernels that applied commit
> 512ac999d275, and should probably be applied to all others as well.

As this commit isn't in a released kernel just yet, we should wait to
see what happens when it hits people's machines, right?

Also, always cc: all of the people involved in the patch you are asking
for, so as to get their opinion.  For some reason this patch did not
have a cc: stable tag on it, was that because the developers did not
think it was relevant for stable kernels?

> The issues introduced by these pathes can be read about on the
> Kubernetes github.
> https://github.com/kubernetes/kubernetes/issues/67577
> 
> It may also be prudent to also apply the not yet accepted patch that
> fixes some introduced compiler warnings discussed here.
> https://lkml.org/lkml/2019/9/18/925

So we should wait for this to hit Linus's tree too, right?

thanks,

greg k-h

  reply	other threads:[~2019-09-25  6:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25  5:53 Please backport de53fd7aedb1 : sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices Dave Chiluk
2019-09-25  6:44 ` Greg KH [this message]
2019-09-27  6:12   ` Dave Chiluk
2019-09-27  6:24     ` Greg KH
2019-09-27 13:13     ` Sasha Levin
2019-10-03  5:15       ` Dave Chiluk
2019-10-03  6:51         ` Greg KH
2019-10-18 20:23           ` Dave Chiluk
2019-10-18 20:53             ` Peter Zijlstra
2019-10-22 14:55               ` Dave Chiluk
2019-11-04 11:08                 ` Greg KH
2019-11-08 18:06                   ` [PATCH v4.14.y 1/2] " Dave Chiluk
2019-11-08 20:15                   ` [PATCH v4.14.y 0/2] Please backport de53fd7aedb1 : " Dave Chiluk
2019-11-08 20:15                     ` [PATCH v4.14.y 1/2] " Dave Chiluk
2019-11-08 20:15                     ` [PATCH v4.14.y 2/2] sched/fair: Fix -Wunused-but-set-variable warnings Dave Chiluk
2019-11-11  9:18                     ` [PATCH v4.14.y 0/2] Please backport de53fd7aedb1 : sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices Greg KH
2019-11-08 20:20                   ` [PATCH v4.19.y " Dave Chiluk
2019-11-08 20:20                     ` [PATCH v4.19.y 1/2] " Dave Chiluk
2019-11-08 20:20                     ` [PATCH v4.19.y 2/2] sched/fair: Fix -Wunused-but-set-variable warnings Dave Chiluk
2019-11-11  9:19                     ` [PATCH v4.19.y 0/2] Please backport de53fd7aedb1 : sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices Greg KH

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=20190925064414.GA1449297@kroah.com \
    --to=greg@kroah.com \
    --cc=chiluk+linux@indeed.com \
    --cc=stable@vger.kernel.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