From: Jiri Slaby <jirislaby@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mike Galbraith <efault@gmx.de>,
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: Wed, 16 Feb 2011 09:55:04 +0100 [thread overview]
Message-ID: <4D5B90E8.6080605@gmail.com> (raw)
In-Reply-To: <20110216082559.GA16529@elte.hu>
On 02/16/2011 09:25 AM, Ingo Molnar wrote:
>
> * Mike Galbraith <efault@gmx.de> wrote:
>
>> On Tue, 2011-02-15 at 18:02 -0500, Steven Rostedt wrote:
>>> [ Added LKML ]
>>>
>>> On Tue, 2011-02-15 at 13:17 -0800, gregkh@suse.de wrote:
>>>> This is a note to let you know that I've just added the patch titled
>>>>
>>>> sched: Give CPU bound RT tasks preference
>>>>
>>>> to the 2.6.32-longterm tree which can be found at:
>>>> http://www.kernel.org/git/?p=linux/kernel/git/longterm/longterm-queue-2.6.32.git;a=summary
>>>>
>>>> The filename of the patch is:
>>>> 0006-sched-Give-CPU-bound-RT-tasks-preference.patch
>>>> and it can be found in the queue-2.6.32 subdirectory.
>>>>
>>>> If you, or anyone else, feels it should not be added to the 2.6.32 longterm tree,
>>>> please let <stable@kernel.org> know about it.
>>>>
>>>>
>>>
>>> I don't mind this patch being added to the long term tree. But I'm
>>> curious about what is the criteria for adding changes to it? This is a
>>> performance improvement and not a critical bug fix.
>>
>> Yes, I added it for the performance. .32-stable is enterprise beans and
>> biscuits. Same reason I added the load balancing fixes, boxen won't
>> explode without them, but load balancing performs better with them.
>
> We try to concentrate on regression fixes though.
Hi, I cannot fully agree with this. The question is who are "we" here?
If every packager using this stable tree is forced by users/customers to
take it anyway, it's better to have it in stable.
It has several reasons:
* It will have an eye of experts on them. Not that at distro providers
there are no experts, but the authors who are cced here know definitely
the code better.
* Not every packager has to duplicate others work.
* The stable tree changes constantly. Managing hundreds of patches
applied to a stable tree before kernels are being packaged is thus
sometimes a hell. Reducing this number is a good thing(TM).
regards,
--
js
next prev parent reply other threads:[~2011-02-16 8:55 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 [this message]
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
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=4D5B90E8.6080605@gmail.com \
--to=jirislaby@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=ghaskins@novell.com \
--cc=gregkh@suse.de \
--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