From: Bob <spam@homeurl.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Need to enable caches in SMP ? (was Kernel 2.6 SMP very slow with ServerWorks LE Chipset)
Date: Fri, 15 Dec 2006 19:05:03 +0800 [thread overview]
Message-ID: <4582815F.6040906@homeurl.co.uk> (raw)
In-Reply-To: <458189FD.2080805@wolfmountaingroup.com>
Jeff V. Merkey wrote:
> Alan wrote:
>>> As per Alan's suggestion I decompressed the kernel source tree with
>>> the processes pegged to one CPU then the other, and as he predicted
>>> it took vastly longer on one CPU than the other, but I don't know
>>> what that implies, or how to fix it.
>>
>>> From the timing it sounds like one processor cache is disabled which
>>> is a
>> little peculiar to say the least.
>>
> enable the L1 cache in the processor. BIOS settings, no doubt.
>
> Jeff
The very spartan Phoenix BIOS doesn't have any options to enable or
disable CPU Cache, which I know full well to enable, but it does have
something rather vaguely called "Memory Caching" the enabling of which
seems to have fixed the problem, it's strange it only disabled the cache
on one CPU and only under 2.6, I'll investigate more in January.
It's good to have the fix search able, this thread would have saved me
from making an ass of myself.
Thank you for your help.
prev parent reply other threads:[~2006-12-15 11:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 5:43 Kernel 2.6 SMP very slow with ServerWorks LE Chipset Bob
2006-12-07 11:07 ` Alan
2006-12-08 5:34 ` Bob
2006-12-07 11:15 ` Arjan van de Ven
2006-12-08 5:50 ` Bob
2006-12-14 3:09 ` Bob
2006-12-14 11:03 ` Need to enable caches in SMP ? (was Kernel 2.6 SMP very slow with ServerWorks LE Chipset) Alan
2006-12-14 17:29 ` Jeff V. Merkey
2006-12-15 11:05 ` Bob [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=4582815F.6040906@homeurl.co.uk \
--to=spam@homeurl.co.uk \
--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