From: Peter Samuelson <peter@cadcamlab.org>
To: Android <android@abac.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.18 release notes
Date: Mon, 11 Dec 2000 23:39:56 -0600 [thread overview]
Message-ID: <20001211233956.F3199@cadcamlab.org> (raw)
In-Reply-To: <E145f1E-0000a9-00@the-village.bc.nu> <00121121242201.00885@cy60022-a>
In-Reply-To: <00121121242201.00885@cy60022-a>; from android@abac.com on Mon, Dec 11, 2000 at 09:24:22PM +0000
[AC]
> > ... added basic support for the Pentium IV.
[Android]
> How is the Pentium IV more advanced than the Pentium III, other than
> speed? Why would LInux care about a 1500 MHz clock or 400 MHz bus
> speed? Just treat the PIV as a faster PIII.
It all sounds so simple, right? Several small things to worry about:
- CPU identification and categorization. The P4 reports itself as CPU
family 15 rather than family 6 like PPro, PII and PIII. Thus, Linux
code that tests for certain features by saying if(cpufamily==6)
didn't notice that the P4 would work. Also there was at least one
format string like sprintf(buf, "i%d86", cpufamily) which is supposed
to print "i686" but on the P4 would print "i1586"....
- metrics -- L1 cacheline size is the important one: you align array
elements to this size when you want a per-cpu array, so that multiple
CPUs do not share a cacheline for accessing their "own" structure.
Proper alignment avoids "cacheline ping-pong", as it's called,
whenever two CPUs need to access "their" element of the same array at
the same time.
- as to the MHz -- there was a wraparound bug if your CPU is faster
than 2 GHz (highest signed 32-bit int), which isn't a problem today
but will be tomorrow.
- Tigran's microcode driver -- some small changes were made so that it
could be used for P4's.
- maybe they'll need to patch lm_sensors to accommodate the increased
temperature range since the P4 runs so hot. (: (:
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-12 6:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-12 2:18 Linux 2.2.18 release notes Alan Cox
2000-12-11 21:24 ` Android
2000-12-12 5:39 ` Peter Samuelson [this message]
2000-12-12 10:30 ` Bruce Korb
2000-12-12 12:28 ` Alan Cox
2000-12-13 1:24 ` Igmar Palsenberg
2000-12-13 1:28 ` Mark Hahn
2000-12-12 3:30 ` Paul Fulghum
2000-12-12 3:47 ` Peter Samuelson
2000-12-12 12:26 ` Alan Cox
2000-12-12 12:28 ` Lars Marowsky-Bree
2000-12-12 11:31 ` David Weinehall
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=20001211233956.F3199@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=android@abac.com \
--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