From: Dave Chiluk <chiluk+linux@indeed.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ben Segall <bsegall@google.com>, Phil Auld <pauld@redhat.com>,
stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Qian Cai <cai@lca.pw>
Subject: [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
Date: Fri, 8 Nov 2019 14:20:06 -0600 [thread overview]
Message-ID: <1573244408-31101-1-git-send-email-chiluk+linux@indeed.com> (raw)
In-Reply-To: <20191104110832.GE1945210@kroah.com>
Here's the backported patches for 4.19.y. Logic is basically the same, the
issue was primarily with patch context. The patches are really back-ports and
not cherry-picks because of that, if that's an issue feel free to change the
text description.
[PATCH v4.19.y 1/2] sched/fair: Fix low cpu usage with high throttling by
[PATCH v4.19.y 2/2] sched/fair: Fix -Wunused-but-set-variable warnings
next prev parent reply other threads:[~2019-11-08 20:20 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
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 ` Dave Chiluk [this message]
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=1573244408-31101-1-git-send-email-chiluk+linux@indeed.com \
--to=chiluk+linux@indeed.com \
--cc=bsegall@google.com \
--cc=cai@lca.pw \
--cc=gregkh@linuxfoundation.org \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=sashal@kernel.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;
as well as URLs for NNTP newsgroup(s).