From: Alan <alan@lxorguk.ukuu.org.uk>
To: Bob <spam@homeurl.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Need to enable caches in SMP ? (was Kernel 2.6 SMP very slow with ServerWorks LE Chipset)
Date: Thu, 14 Dec 2006 11:03:24 +0000 [thread overview]
Message-ID: <20061214110324.780b4bf0@localhost.localdomain> (raw)
In-Reply-To: <4580C054.2080902@homeurl.co.uk>
> 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.
Alan
next prev parent reply other threads:[~2006-12-14 10:55 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 ` Alan [this message]
2006-12-14 17:29 ` Need to enable caches in SMP ? (was Kernel 2.6 SMP very slow with ServerWorks LE Chipset) Jeff V. Merkey
2006-12-15 11:05 ` Bob
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=20061214110324.780b4bf0@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=spam@homeurl.co.uk \
/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