From: Sasha Levin <sashal@kernel.org>
To: Dave Chiluk <chiluk+linux@indeed.com>
Cc: Greg KH <greg@kroah.com>, Ben Segall <bsegall@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Phil Auld <pauld@redhat.com>,
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: Fri, 27 Sep 2019 09:13:32 -0400 [thread overview]
Message-ID: <20190927131332.GO8171@sasha-vm> (raw)
In-Reply-To: <CAC=E7cXcujmbwMnmXeH2=80Lkki+j_b=WE4KCWaM1mYafDaWSA@mail.gmail.com>
On Fri, Sep 27, 2019 at 01:12:40AM -0500, Dave Chiluk wrote:
>On Wed, Sep 25, 2019 at 1:44 AM Greg KH <greg@kroah.com> wrote:
>>
>> 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?
>
>I think waiting till 5.4 is released would be irresponsible on this
>one. 512ac999 was recently pushed back into many of the distro
The "released kernel" statement means 5.4-rc1 rather than 5.4, which is
just a few days away.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-09-27 13:13 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
2019-09-27 6:12 ` Dave Chiluk
2019-09-27 6:24 ` Greg KH
2019-09-27 13:13 ` Sasha Levin [this message]
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=20190927131332.GO8171@sasha-vm \
--to=sashal@kernel.org \
--cc=bsegall@google.com \
--cc=chiluk+linux@indeed.com \
--cc=greg@kroah.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--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