From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Anton Starikov <ant.starikov@gmail.com>, Greg KH <greg@kroah.com>,
stable@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [Bugme-new] [Bug 15618] New: 2.6.18->2.6.32->2.6.33 huge regression in performance
Date: Wed, 24 Mar 2010 00:36:40 +0100 [thread overview]
Message-ID: <20100323233640.GA16798@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.00.1003231602130.18017@i5.linux-foundation.org>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>
> On Tue, 23 Mar 2010, Anton Starikov wrote:
> >
> > I think we got a winner!
> >
> > Problem seems to be fixed.
> >
> > Just for record, I used next patches:
> >
> > 59c33fa7791e9948ba467c2b83e307a0d087ab49
> > 5d0b7235d83eefdafda300656e97d368afcafc9a
> > 1838ef1d782f7527e6defe87e180598622d2d071
> > 4126faf0ab7417fbc6eb99fb0fd407e01e9e9dfe
> > bafaecd11df15ad5b1e598adc7736afcd38ee13d
> > 0d1622d7f526311d87d7da2ee7dd14b73e45d3fc
>
> Ok. If you have performance numbers for before/after these patches for
> your actual workload, I'd suggest posting them to stable@kernel.org, and
> maybe those rwsem fixes will get back-ported.
>
> The patches are pretty small, and should be fairly safe. So they are
> certainly stable material.
We havent had any stability problems with them, except one trivial build bug,
so -stable would be nice.
Ingo
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-03-23 23:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15618-10286@https.bugzilla.kernel.org/>
2010-03-23 14:22 ` Andrew Morton
2010-03-23 17:34 ` Ingo Molnar
2010-03-23 17:45 ` Linus Torvalds
2010-03-23 17:57 ` Anton Starikov
2010-03-23 18:00 ` Ingo Molnar
2010-03-23 18:03 ` Anton Starikov
2010-03-23 18:21 ` Andrew Morton
2010-03-23 18:25 ` Anton Starikov
2010-03-23 19:22 ` Robin Holt
2010-03-23 19:30 ` Anton Starikov
2010-03-23 19:49 ` Robin Holt
2010-03-23 19:57 ` Robin Holt
2010-03-23 19:50 ` Anton Starikov
2010-03-23 19:52 ` Linus Torvalds
2010-03-24 16:40 ` Roland Dreier
2010-03-26 3:24 ` Anton Starikov
2010-03-23 19:14 ` Anton Starikov
2010-03-23 19:17 ` Peter Zijlstra
2010-03-23 19:42 ` Anton Starikov
2010-03-23 19:54 ` Linus Torvalds
2010-03-23 20:43 ` Anton Starikov
2010-03-23 23:04 ` Linus Torvalds
2010-03-23 23:19 ` Anton Starikov
2010-03-23 23:36 ` Ingo Molnar [this message]
2010-03-23 23:55 ` Linus Torvalds
2010-03-24 0:03 ` Anton Starikov
2010-03-24 2:15 ` Andi Kleen
2010-03-24 3:00 ` Linus Torvalds
2010-04-19 18:19 ` Greg KH
2010-03-23 18:13 ` Andrew Morton
2010-03-23 18:19 ` Anton Starikov
2010-03-23 18:27 ` Ingo Molnar
2010-03-23 21:19 ` Anton Starikov
2010-04-02 18:57 ` Lee Schermerhorn
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=20100323233640.GA16798@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=ant.starikov@gmail.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@kernel.org \
--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