From: Greg KH <greg@kroah.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andi Kleen <andi@firstfloor.org>,
"lee.schermerhorn@hp.com" <lee.schermerhorn@hp.com>,
"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
stable@kernel.org, Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [stable] aim7 scalability issue on 4 socket machine
Date: Sun, 6 Dec 2009 14:17:34 -0800 [thread overview]
Message-ID: <20091206221734.GA22414@kroah.com> (raw)
In-Reply-To: <20091206211105.GA13917@elf.ucw.cz>
On Sun, Dec 06, 2009 at 10:11:05PM +0100, Pavel Machek wrote:
> On Sun 2009-12-06 21:11:36, Andi Kleen wrote:
> > > - It must be obviously correct and tested.
> > > - It cannot be bigger than 100 lines, with context.
> > > - It must fix only one thing.
> > > - It must fix a real bug that bothers people (not a, "This could be a
> > > problem..." type thing).
> >
> > A significant slow down in a common situation is a "significant
> > bug that bothers people"
>
> Well, IIRC it was benchmark that was slowed down, on huge system, so
> it was exactly "this could be a problem".
>
> Anyway, I don't care about -stable series too much (and sorry for
> replying to such an old mail), but perhaps the docs should be updated?
>
> Examples cited there are such as "data corruption" or "oops", which is
> clearly different ballpark then "slowdown".
Why does it really matter if the intent is the thing that matters here.
Deal with specifics on a case-by-case basis, and if you don't really
care about this, then why dig up a many-month old thread?
strange,
greg k-h
next prev parent reply other threads:[~2009-12-06 22:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 9:31 aim7 scalability issue on 4 socket machine Zhang, Yanmin
2009-09-17 9:40 ` Peter Zijlstra
2009-09-17 10:35 ` Hugh Dickins
2009-09-18 2:02 ` Zhang, Yanmin
2009-09-18 2:59 ` Andrew Morton
2009-09-18 3:17 ` Zhang, Yanmin
2009-09-18 6:53 ` Hugh Dickins
2009-09-18 7:05 ` Andrew Morton
2009-12-06 20:08 ` Pavel Machek
2009-12-06 20:11 ` Andi Kleen
2009-12-06 21:11 ` Pavel Machek
2009-12-06 22:17 ` Greg KH [this message]
2009-12-06 22:23 ` [stable] " Pavel Machek
2009-09-18 7:12 ` Andi Kleen
2009-09-18 7:29 ` Hugh Dickins
2009-09-18 13:15 ` Lee Schermerhorn
2009-09-18 14:33 ` Andi Kleen
2009-09-17 10:35 ` Ingo Molnar
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=20091206221734.GA22414@kroah.com \
--to=greg@kroah.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=stable@kernel.org \
--cc=yanmin_zhang@linux.intel.com \
/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