Path: utzoo!mnetor!uunet!husc6!bloom-beacon!mit-eddie!ll-xn!ames!amdahl!drivax!alexande From: alexande@drivax.UUCP (Mark Alexander) Newsgroups: comp.arch Subject: Re: Is the Intel memory model safe from NO-ONE ?!? Message-ID: <3384@drivax.UUCP> Date: 9 May 88 17:37:42 GMT References: <1806@obiwan.mips.COM> <2904@omepd> <353@cf-cm.UUCP> Reply-To: alexande@drivax.UUCP (Mark Alexander) Organization: Bob-ist Temple of Monterey Lines: 18 Keywords: 386 intel memory protection management model segmented In article <353@cf-cm.UUCP> mch@computing-maths.cardiff.ac.uk (Major Kano) writes about: >... the advantages of segmenting, ie., ease of doing >relocatable code, logical program design (code, data/heap stack separation), >inter-task separation (LDT's) and a few other related features. Maybe I'm slow, but I can't see how segmentation makes these things much easier, compared with a typical non-segmented paging system. We did a port of FlexOS to both the 386 and the NEC V60, and the V60 was actually easier to deal with precisely because we didn't have to muck with all that segment stuff. And on the V60 it was very easy to achieve all these Nice Things you mentioned, like code/data separation, relocatability, inter-task protection, etc. Hoping someone can explain this to me in a followup article. -- Mark Alexander (UUCP: amdahl!drivax!alexande) "Bob-ism: the Faith that changes to meet YOUR needs." --Bob (as heard on PHC)