Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!oliveb!intelca!mipos3!kds
From: kds@mipos3.UUCP
Newsgroups: comp.arch
Subject: Re: 64 Vs 32 (386 addressing)
Message-ID: <557@mipos3.UUCP>
Date: Fri, 20-Mar-87 21:31:53 EST
Article-I.D.: mipos3.557
Posted: Fri Mar 20 21:31:53 1987
Date-Received: Sun, 22-Mar-87 22:59:14 EST
References: <3810013@nucsrl.UUCP> <28200016@ccvaxa> <4372@utcsri.UUCP> <390@nvanbc.UUCP>
Reply-To: kds@mipos3.UUCP (Ken Shoemaker ~)
Organization: Intel, Santa Clara, CA
Lines: 16

>Also there is another bit which says whether the segment size is in bytes
>or increments of (I think) 16 bytes, this is how you can have segments up
>to 1Mb now.

actually, the bit indicates whether the segment size is in bytes or pages
(4k) increments.  This allows segments up to 4 GBytes.
-- 
The above views are personal.

The primary reason innumeracy is so pernicious is the ease with which numbers
are invoked to bludgeon the innumerate into dumb acquiescence.
			- John Allen Paulos

Ken Shoemaker, Microprocessor Design, Intel Corp., Santa Clara, California
uucp: ...{hplabs|decwrl|amdcad|qantel|pur-ee|scgvaxd|oliveb}!intelca!mipos3!kds
csnet/arpanet: kds@mipos3.intel.com