From: Andi Kleen <ak@suse.de>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, garloff@suse.de, ak@suse.de
Subject: Re: 2.6.11 vs 2.6.10 slowdown on i686
Date: Thu, 17 Mar 2005 19:36:32 +0100 [thread overview]
Message-ID: <20050317183632.GC12725@wotan.suse.de> (raw)
In-Reply-To: <E1DBtvc-0002c4-00@mta1.cl.cam.ac.uk>
On Thu, Mar 17, 2005 at 12:16:40PM +0000, Ian Pratt wrote:
>
> Folks,
>
> When we upgraded arch xen/x86 to kernel 2.6.11, we noticed a slowdown
> on a number of micro-benchmarks. In order to investigate, I built
> native (non Xen) i686 uniprocessor kernels for 2.6.10 and 2.6.11 with
> the same configuration and ran lmbench-3.0-a3 on them. The test
> machine was a 2.4GHz Xeon box, gcc 3.3.3 (FC3 default) was used to
> compile the kernels, NOHIGHMEM=y (2-level only).
Hmm, it is known that x86-64 performance is down because it touches
a lot more memory now on fork/exit. I have some optimizations planned to fix
that, in fact it should be faster in the end.
i386 slowdowns are unexpected though.
I remember I tested i386 briefly with lmbench with my original 4level
patch, and there werent any significant slowdowns. However the patch
that eventually went into mainline was very different and in particular
clear_page_range() which is very critical looks completely different
now and does more work than before. Perhaps the slowdown happens in this
area.
diffprofile of before and after would be interesting.
-Andi
prev parent reply other threads:[~2005-03-17 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 12:16 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
2005-03-17 18:36 ` Andi Kleen [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=20050317183632.GC12725@wotan.suse.de \
--to=ak@suse.de \
--cc=Ian.Pratt@cl.cam.ac.uk \
--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
Powered by JetHome