From: Mike Haertel <9fans@ducky.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 386
Date: Sun, 30 Oct 2005 13:27:15 -0800 [thread overview]
Message-ID: <200510302127.j9ULRFT3026074@ducky.net> (raw)
In-Reply-To: <9754e46bd89fc67ac49939b849c4e414@plan9.bell-labs.com>
jmk wrote:
>If you keep the 486 then there is no point in removing the 386,
>you would gain nothing.
Just to clarify exactly what the differences are, the 486 added:
* Integrated floating point (and better IEEE 754 conformance)
* CR0.WP control bit -- allows copy-on-write paging strategies
even for accesses from ring 0 (386 didn't honor page write
protection when CPU was in kernel mode)
* New instructions:
* BSWAP
* CMPXCHG
* XADD
* INVD
* WBINVD
I agree with jmk that Plan 9 would be unlikely to gain much, since:
* Plan 9 on the 386 already requires a 387, and Plan 9 is not
pedantic about IEEE 754
* Historically Plan 9 has not been concerned with the kind
of pedal-to-the-metal optimization that would benefit
from CR0.WP, BSWAP, CMPXCHG, or XADD.
* There is rarely any good reason to use WBINVD, and almost
never a good reason to use INVD (except maybe in the BIOS),
since x86 systems are cache coherent.
next prev parent reply other threads:[~2005-10-30 21:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 15:08 Russ Cox
2005-10-29 15:26 ` Lucio De Re
2005-10-29 19:07 ` William Josephson
2005-10-29 20:01 ` jmk
2005-10-29 20:06 ` Lucio De Re
2005-10-29 21:07 ` Uriel
2005-10-29 21:18 ` jmk
2005-10-29 21:51 ` Ronald G Minnich
2005-10-29 22:31 ` Francisco J Ballesteros
2005-10-30 0:50 ` Ronald G Minnich
2005-10-30 5:41 ` Jack Johnson
2005-10-30 16:15 ` Ronald G Minnich
2005-10-30 20:02 ` jmk
2005-10-30 20:12 ` Uriel
2005-10-30 20:34 ` Devon H. O'Dell
2005-10-30 20:52 ` jmk
2005-10-30 21:15 ` Devon H. O'Dell
2005-10-30 22:56 ` jmk
2005-10-31 0:20 ` Ronald G Minnich
2005-10-31 0:49 ` Russ Cox
2005-10-31 21:26 ` Dave Eckhardt
2005-10-30 21:27 ` Mike Haertel [this message]
2005-10-31 10:06 ` Charles Forsyth
2005-10-30 22:11 ` Ronald G Minnich
2005-10-30 21:16 ` Francisco J Ballesteros
2005-10-30 21:53 ` Ronald G Minnich
2005-10-29 23:45 ` John DeGood
2005-10-30 0:04 ` William Josephson
2005-10-30 12:59 ` Brantley Coile
2005-10-30 1:14 ` geoff
2005-10-29 20:22 ` Christopher Nielsen
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=200510302127.j9ULRFT3026074@ducky.net \
--to=9fans@ducky.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).