From: Andi Kleen <ak@suse.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: tim.c.chen@linux.intel.com, Adrian Bunk <bunk@stusta.de>,
linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: 2.6.19-rc1: x86_64 slowdown in lmbench's fork
Date: Fri, 3 Nov 2006 18:47:49 +0100 [thread overview]
Message-ID: <200611031847.49222.ak@suse.de> (raw)
In-Reply-To: <m1lkmsxwk7.fsf@ebiederm.dsl.xmission.com>
> So unless there is some other array that is sized by NR_IRQs
> in the context switch path which could account for this in
> other ways. It looks like you just got unlucky.
TLB/cache profiling data might be useful?
My bet would be more on cache effects.
> The only hypothesis that I can seem to come up with is that maybe
> you are getting an extra tlb now that you didn't use to.
> I think the per cpu area is covered by huge pages but maybe not.
It should be.
-Andi
next prev parent reply other threads:[~2006-11-03 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 16:44 2.6.19-rc1: Slowdown in lmbench's fork Tim Chen
2006-11-02 18:33 ` Eric W. Biederman
2006-11-02 18:34 ` Tim Chen
2006-11-03 2:11 ` 2.6.19-rc1: x86_64 slowdown " Adrian Bunk
2006-11-03 9:08 ` Eric W. Biederman
2006-11-03 16:10 ` Tim Chen
2006-11-03 17:35 ` Eric W. Biederman
2006-11-03 17:47 ` Andi Kleen [this message]
2006-11-03 18:18 ` Eric W. Biederman
2006-11-03 18:39 ` Andi Kleen
2006-11-03 20:25 ` Tim Chen
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=200611031847.49222.ak@suse.de \
--to=ak@suse.de \
--cc=bunk@stusta.de \
--cc=discuss@x86-64.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.c.chen@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