From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Kurt Garloff <garloff@suse.de>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>,
Ian Pratt <Ian.Pratt@cl.cam.ac.uk>, Andi Kleen <ak@suse.de>
Subject: Re: 2.6.11 vs 2.6.10 slowdown on i686
Date: Fri, 18 Mar 2005 19:46:33 +1100 [thread overview]
Message-ID: <423A9569.3040105@yahoo.com.au> (raw)
In-Reply-To: <20050318082554.GA12536@tpkurt.garloff.de>
Kurt Garloff wrote:
> Hi Nick,
>
Hi Kurt!
> On Thu, Mar 17, 2005 at 11:37:24PM +1100, Nick Piggin wrote:
>
>>Ian Pratt wrote:
>>
>>>fork: 166 -> 235 (40% slowdown)
>>>exec: 857 -> 1003 (17% slowdown)
>>>
>>>I'm guessing this is down to the 4 level pagetables. This is rather a
>>>surprise as I thought the compiler would optimise most of these
>>>changes away. Apparently not.
>>
>>There are some changes in the current -bk tree (which are a
>>bit in-flux at the moment) which introduce some optimisations.
>>
>>They should bring 2-level performance close to par with 2.6.10.
>>If not, complain again :)
>
>
> Is there a clean patchset that we should look at to test?
>
Probably the best thing would be to wait and see what happens
with the ptwalk patches. There is a fix in there for ia64 now,
but I think that may be a temporary one.
Andi is probably keeping an eye on that, but if not then I
could put a patchset together when things finalise in 2.6.
From the profiles I have seen, the ptwalk patches bring page
table walking performance pretty well back to 2.6.10 levels,
however the "aggressive page table freeing" (clear_page_range)
changes that went in at the same time as the 4level stuff
seem to be what is slowing down exit() and unmapping performance.
Not by a huge amount, mind you, and it is not completely wasted
performance, because it provides better page table freeing.
But it is enough to be annoying! I haven't had much time to look
at it lately, but I hope to get onto it soon.
Nick
next prev parent reply other threads:[~2005-03-18 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 12:16 2.6.11 vs 2.6.10 slowdown on i686 Ian Pratt
2005-03-17 12:37 ` Nick Piggin
2005-03-17 20:23 ` Ian Pratt
2005-03-18 8:25 ` Kurt Garloff
2005-03-18 8:46 ` Nick Piggin [this message]
2005-03-17 18:36 ` Andi Kleen
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=423A9569.3040105@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=ak@suse.de \
--cc=garloff@suse.de \
--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