From: Adrian Bunk <bunk@stusta.de>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org, ak@suse.de, discuss@x86-64.org
Subject: Re: 2.6.19-rc1: x86_64 slowdown in lmbench's fork
Date: Fri, 3 Nov 2006 03:11:45 +0100 [thread overview]
Message-ID: <20061103021145.GD13381@stusta.de> (raw)
In-Reply-To: <1162492453.10806.75.camel@localhost.localdomain>
On Thu, Nov 02, 2006 at 10:34:13AM -0800, Tim Chen wrote:
> On Thu, 2006-11-02 at 11:33 -0700, Eric W. Biederman wrote:
>
> > My only partial guess is that it might be worth adding the per cpu
> > variables my patch adds without any of the corresponding code changes.
> > And see if adding variables to the per cpu area is what is causing the
> > change.
> >
> > The two tests I can see in this line are:
> > - to add the percpu vector_irq variable.
> > - to increase NR_IRQs.
>
> Increasing the NR_IRQs resulted in the regression.
>...
What's your CONFIG_NR_CPUS setting that you are seeing such a big
regression?
> Tim
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-11-03 2:11 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 ` Adrian Bunk [this message]
2006-11-03 9:08 ` 2.6.19-rc1: x86_64 slowdown " 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
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=20061103021145.GD13381@stusta.de \
--to=bunk@stusta.de \
--cc=ak@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.