public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Mike Galbraith <efault@gmx.de>
Cc: Jiri Slaby <jirislaby@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	Steven Rostedt <rostedt@goodmis.org>,
	gregkh@suse.de, srostedt <srostedt@redhat.com>,
	a.p.zijlstra@chello.nl, ghaskins@novell.com, stable@kernel.org,
	stable-commits@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Patch "sched: Give CPU bound RT tasks preference" has been added to the 2.6.32-longterm tree
Date: Thu, 17 Feb 2011 08:52:19 +0100	[thread overview]
Message-ID: <20110217085219.417ba829@stein> (raw)
In-Reply-To: <1297919107.6361.59.camel@marge.simson.net>

On Feb 17 Mike Galbraith wrote:
> On Wed, 2011-02-16 at 15:29 +0100, Stefan Richter wrote:
> > Jiri,
> > if the desire is to improve performance of existing features (and maybe
> > add this and that little feature that looks attractive), while at the same
> > time you want
> >   - experts to have looked at these improvements,
> >   - packagers to avoid duplicate work,
> >   - keep the number of local patches in check,
> > then the solution is to /stay close enough to the mainline/.

[By which I meant updating, not backporting.]

> That's the intent of pushing more than _purely_ critical bugfixes, get a
> bit closer.  Enterprise can't move as fast as mainline, not even close,
> that's a given.  Stable problem get griped about though, so there's no
> choice but to take some risk.  The tricky bit is how much, and how you
> go about it.

Granted.

> People are fixing this and that in their enterprise kernels privately
> every day.  The only difference between that, and pushing baked fixes
> back is that pushing to stable is visible.  I strongly suspect that
> there are just tons of mainline backports sitting in each and every
> enterprise tree in existence.

'Visible' = the change which was an important performance improvement or
outright fix at site A (and a nice-to-have improvement on sites B...X)
eventually exhibits a regression at site Y.
-- 
Stefan Richter
-=====-==-== --=- =---=
http://arcgraph.de/sr/

  parent reply	other threads:[~2011-02-17  7:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <12978046423644@kroah.org>
2011-02-15 23:02 ` Patch "sched: Give CPU bound RT tasks preference" has been added to the 2.6.32-longterm tree Steven Rostedt
2011-02-15 23:32   ` Greg KH
2011-02-16  2:46     ` Mike Galbraith
2011-02-16  2:01   ` Mike Galbraith
2011-02-16  2:03     ` Steven Rostedt
2011-02-16  8:25     ` Ingo Molnar
2011-02-16  8:55       ` Jiri Slaby
2011-02-16  9:22         ` Ingo Molnar
2011-02-16  9:45         ` Mike Galbraith
2011-02-16 14:29           ` Stefan Richter
2011-02-17  5:05             ` Mike Galbraith
2011-02-17  6:22               ` [stable] " Willy Tarreau
2011-02-17  7:52               ` Stefan Richter [this message]
2011-02-17  9:41                 ` Mike Galbraith
2011-02-17 14:28                   ` Stefan Richter

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=20110217085219.417ba829@stein \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=efault@gmx.de \
    --cc=ghaskins@novell.com \
    --cc=gregkh@suse.de \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=srostedt@redhat.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@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