From: Ingo Molnar <mingo@kernel.org>
To: Ben Guthro <ben@guthro.net>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mike Galbraith <efault@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Potential scheduler regression
Date: Tue, 11 Jul 2017 10:30:14 +0200 [thread overview]
Message-ID: <20170711083014.jpdpcbo6rlh5uuti@gmail.com> (raw)
In-Reply-To: <CAOvdn6U0cFStU0-Sh=NkjNqjDW=y4iy_S7x0t=jnw__eY1ahOA@mail.gmail.com>
* Ben Guthro <ben@guthro.net> wrote:
> > If people have experience with these in the "enterprise" distros, or any other
> > tree, and want to provide me with backported, and tested, patches, I'll be
> > glad to consider them for stable kernels.
> >
> > thanks,
> >
> > greg k-h
>
> I tried to do a simple cherry-pick of the suggested patches - but they
> apply against files that don't exist in the 4.9 series.
I think there are only two strategies to maintain a backport which work in the
long run:
- insist on the simplest fixes and pure cherry-picks
- or pick up _everything_ to sync up the two versions.
The latter would mean a lot of commits - and I'm afraid it would also involve the
scheduler header split-up, which literally involves hundreds of files plus
perpetual build-breakage risk, so it's a no-no.
> In my release of 4.9 - I'm planning on doing the simpler revert of 1b568f0aab
> that introduced the performance degradation, rather than pulling in lots of code
> from newer kernels.
That sounds much saner - I'd even Ack that approach for -stable as a special
exception, than to complicate things with excessive backports.
Thanks,
Ingo
next prev parent reply other threads:[~2017-07-11 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 15:42 Ben Guthro
2017-07-05 16:48 ` Peter Zijlstra
2017-07-07 20:55 ` Ben Guthro
2017-07-10 9:25 ` Peter Zijlstra
2017-07-10 15:26 ` Greg KH
2017-07-10 15:43 ` Ben Guthro
2017-07-11 8:30 ` Ingo Molnar [this message]
2017-07-11 9:55 ` Greg KH
2017-07-13 19:24 ` Ben Guthro
2017-07-14 6:54 ` Greg KH
2017-07-19 8:02 ` 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=20170711083014.jpdpcbo6rlh5uuti@gmail.com \
--to=mingo@kernel.org \
--cc=ben@guthro.net \
--cc=efault@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.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