Re: '586 Feature Ideas

Article View: comp.arch

Article #11872

#11872

From: David Feustel
Date: Thu, 30 May 1991 02:49

10 lines
1046 bytes

What's needed even more is optional per/segment page tables.
i.e. a separate page table for each segment when so desired. This
would overcome the current 486 limitation that any accessible segment
must be completely mapped into one 32-bit virtual address space.
The implication of this limitation is that, if you want to address
6 or more segments simultaneously, no segment can be greater than
1/8th of the address space (=512megabytes).
-- 
David Feustel, 1930 Curdes Ave, Fort Wayne, IN 46805, (219) 482-9631
EMAIL: feustel@netcom.com  or feustel@cvax.ipfw.indiana.edu

Technical Details

Message-ID: <1991May30.024951.655@netcom.COM>

Path:

arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!netcomsv!feustel

References: <1991May29.190703.12277@kestrel.edu>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!netcomsv!feustel
From: feustel@netcom.COM (David Feustel)
Newsgroups: comp.arch
Subject: Re: '586 Feature Ideas
Keywords: 80586, segment, pointer
Message-ID: <1991May30.024951.655@netcom.COM>
Date: 30 May 91 02:49:51 GMT
References: <1991May29.190703.12277@kestrel.edu>
Distribution: comp.arch
Organization: DAFCO - An OS/2 Oasis
Lines: 10

Reply to Parent Message