lkml.org 
[lkml]   [2006]   [Nov]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 2.6.19-rc1: x86_64 slowdown in lmbench's fork
Date
Tim Chen <tim.c.chen@linux.intel.com> writes:

> On Fri, 2006-11-03 at 03:11 +0100, Adrian Bunk wrote:
>
>>
>> What's your CONFIG_NR_CPUS setting that you are seeing such a big
>> regression?
>>
>
> CONFIG_NR_CPUS is set to 8.

Ugh. This simply changes NR_IRQS from 256 to 512. Changing
the size of data from 1K to 2K.

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.

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.

Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-11-03 18:39    [W:0.654 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site