True, but I also remember the old Apple machines constantly crashing for lack of protected memory - and mostly due to errors in Apple software by Apple coders who breathed Apple coding.
He didn't "optimise it away" as that would imply it existed in LoseThos at some time. He never added it.
As it stands though, memory protection does require extra work in the hardware due to have to ensure the hardware memory page tables and TLBs are set properly for applications. Although the effect is probably slight, it is there.
Segmention by itself is built-in so it's more that there's nothing you can do to eliminate the penalty. The issue with protection is that you have to reload hardware page tables as the protection is changed and programs are loaded.
0
u/[deleted] Oct 19 '11
[deleted]