From: Dave Chiluk <chiluk+linux@indeed.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Greg KH <gregkh@linuxfoundation.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>
Subject: Re: Please backport de53fd7aedb1 : sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices
Date: Tue, 22 Oct 2019 09:55:58 -0500 [thread overview]
Message-ID: <CAC=E7cV2DzpLOz_RaFzBKCN3cEntB7BPLGL9PaGZ2LYb6dc0Jw@mail.gmail.com> (raw)
In-Reply-To: <20191018205326.GB1817@hirez.programming.kicks-ass.net>
On Fri, Oct 18, 2019 at 3:53 PM Peter Zijlstra <peterz@infradead.org> wrote:
>
> On Fri, Oct 18, 2019 at 03:23:02PM -0500, Dave Chiluk wrote:
> > @Ben @Ingo @Peter
> > Can you please please ack this backport request?
> >
> > Thank you,
> > Dave Chiluk
> >
> > On Thu, Oct 3, 2019 at 1:51 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Thu, Oct 03, 2019 at 12:15:02AM -0500, Dave Chiluk wrote:
> > > > @Greg KH, Qian Cai's compiler warning fix has now been integrated into
> > > > Linus' tree as commit: 763a9ec06c409
> > > >
> > > > Both de53fd7aedb1 and 763a9ec06c40 are now apart of v5.4-rc1. Can you
> > > > please queue up these fixes for backport to all stable kernels.
> > >
> > > I need an ack from the scheduler maintainers that this is ok to do so...
>
> Sure I suppose, but what makes this commit special? Don't you normally
> take just about anything?
I think this is more a matter of me being a relatively unknown in the
scheduler space, and Greg is just being responsible as this looks like
a pretty scary fix.
In reality, I probably should have just added "Cc:
stable@vger.kernel.org" to the sign-off area of the initial commit and
this conversation wouldn't have been necessary.
next prev parent reply other threads:[~2019-10-22 14:56 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 [this message]
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='CAC=E7cV2DzpLOz_RaFzBKCN3cEntB7BPLGL9PaGZ2LYb6dc0Jw@mail.gmail.com' \
--to=chiluk+linux@indeed.com \
--cc=bsegall@google.com \
--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).