From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.0-rc4
Date: Wed, 22 Jun 2011 21:28:24 -0700 [thread overview]
Message-ID: <BANLkTiksHMkPr-ZXJ6iCpUCupmpapU5D2Q@mail.gmail.com> (raw)
In-Reply-To: <m2boxp39zz.fsf@firstfloor.org>
On Wed, Jun 22, 2011 at 1:08 PM, Andi Kleen <andi@firstfloor.org> wrote:
> Linus Torvalds <torvalds@linux-foundation.org> writes:
>
>> and the
>> conversion from spinlocks to mutexes for the anon_vma locking ended up
>> causing a scalability issue that required fixing.
>
> FWIW it's still ~16% slower. Does that count as fixed?
Well, so far I haven't really seen any suggestions on how to improve
it much further.
3.0 will still be noticeably faster than 2.6.39 due to the other
changes made (ie the read-ahead), so yes, the regression itself is
fixed.
But performance on that particular benchmark with that particular
machine is clearly not optimal, in that there are known setups that
would be faster still.
Of course, the reason for the mutex conversion was _other_ loads,
where the spinlocks had bad behavior. So it's a balancing act. And I
suspect we've reached a reasonable point in that balancing, yes.
Linus
prev parent reply other threads:[~2011-06-23 4:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 4:02 Linus Torvalds
2011-06-21 7:13 ` Linux 3.0-rc4 - fail to compile Paul Rolland
2011-06-21 7:27 ` KAMEZAWA Hiroyuki
2011-06-21 8:08 ` Paul Rolland
2011-06-21 7:43 ` Deng, Xuyue
2011-06-21 15:05 ` Linux 3.0-rc4 Nick Bowler
2011-06-21 15:13 ` Paul Rolland
2011-06-21 16:52 ` Melchior FRANZ
2011-06-22 20:08 ` Andi Kleen
2011-06-23 4:28 ` Linus Torvalds [this message]
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=BANLkTiksHMkPr-ZXJ6iCpUCupmpapU5D2Q@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®