From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Dual XEON - >>SLOW<< on SMP
Date: Tue, 7 Nov 2000 23:10:57 +0100 [thread overview]
Message-ID: <20001107231056.A23564@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0011021334170.83-100000@rc.priv.hereintown.net> <Pine.LNX.4.21.0011071401280.4438-100000@sol.compendium-tech.com>
In-Reply-To: <Pine.LNX.4.21.0011071401280.4438-100000@sol.compendium-tech.com>; from kernel@blackhole.compendium-tech.com on Tue, Nov 07, 2000 at 02:02:23PM -0800
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
On Tue, Nov 07, 2000 at 02:02:23PM -0800, Dr. Kelsey Hudson wrote:
> > This machine isn't even a Xeon, just a PIII CuMine on a ServerWorks HeIII
> > chipset.
>
> Strange, I've got a dual Katmai (non-Xeon) and notice the same...
I've just gotten a dual PIII (Coppermine) to my hands. I *think* that
this machine is quite slower as it should be... However, I've got
no old speed values of that box, but...
> CPU0 CPU1
[...]
> NMI: 190856196 190856196
> LOC: 190858464 190858463
...are these two lines okay? I've noticed that as well, but I've not
seen that on UP machines as well...
.oO( Where did I see those MTRR settings? )
MfG, JBG
--
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
"insmod vi.o and there we go..." (Alexander Viro on linux-kernel)
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2000-11-07 22:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 13:50 Dual XEON - >>SLOW<< on SMP Dr. David Gilbert
2000-11-02 13:56 ` kernel
2000-11-02 14:02 ` Richard B. Johnson
2000-11-02 18:09 ` Ulrich Drepper
2000-11-02 18:23 ` Maciej W. Rozycki
2000-11-02 18:26 ` Matti Aarnio
2000-11-02 18:38 ` Chris Meadors
2000-11-02 18:40 ` Richard B. Johnson
2000-11-02 23:39 ` Wakko Warner
2000-11-07 22:02 ` Dr. Kelsey Hudson
2000-11-07 22:10 ` Jan-Benedict Glaw [this message]
2000-11-07 22:16 ` kernel
2000-11-07 22:31 ` Richard B. Johnson
2000-11-07 22:41 ` Keith Owens
2000-11-07 22:55 ` Richard B. Johnson
2000-11-07 23:03 ` Jeff V. Merkey
2000-11-08 14:28 ` Richard B. Johnson
2000-11-08 19:17 ` Jeff V. Merkey
2000-11-11 19:26 ` Marc Lehmann
2000-11-13 6:22 ` Jeff V. Merkey
2000-11-13 8:41 ` James A. Sutherland
2000-11-13 11:51 ` Marc Lehmann
2000-11-07 22:48 ` J . A . Magallon
2000-11-02 14:10 ` Tigran Aivazian
2000-11-02 17:39 ` Dr. David Gilbert
2000-11-03 0:04 ` bert hubert
2000-11-03 16:13 ` Ricky Beam
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=20001107231056.A23564@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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