3 ms·
The core concept described here significantly overlaps with an OS idea from the 90s that sadly didn't go anywhere. The system was Opal, from the OS group at UWa
by PaulDavisThe1st 5y ago
The core concept described here significantly overlaps with an OS idea from the 90s that sadly didn't go anywhere. The system was Opal, from the OS group at UWashington CS&E and in particular Jeff Chase.
The key idea in Opal was to put all processes in the same address space (like Singularity does), but to use hardware systems to provide memory protection (whereas Singularity relies on "software mechanisms"). Communication between processes now becomes as simple as one process giving the other a pointer (obviously it has to refer to a page with appropriate access). As with Singularity, the overhead of TLB flushes and page table management goes away, making context switches much faster (especially for large working set processes). To quote:
> Protection in Opal is independent of the single address space; each Opal thread executes within a protection domain that defines which virtual pages it has the right to access. The rights to access a page can be easily transmitted from one process to another. The result is a much more flexible protection structure, permitting different (and dynamically changing) protection options depending on the trust relationship between cooperating parties. We believe that this organization can improve both the structure and performance of complex, cooperating applications.
You can read lots more about Opal here (it's all quite old now): https://homes.cs.washington.edu/~levy/opal/opal.html https://homes.cs.washington.edu/~levy/opal/opal.html
I still think it's one of the best OS ideas ever, and I'm sad that it never really came to fruition.
- pjmlp 5y agoThanks for sharing the link.