Anyhow, re-reading my last few posts I may have misguided the direction of Unununium so in order to appease myself and ensure I broadcast the right information, here’s a summary of Unununium’s goals:

* Single Address Space
* Dynamic Relocation
* Live Upgrade (no reboot required)
* Open Design
* Approachable Internal Hacking
* Well documented and teachable

Basically, a simple system with the internals clearly visible and inspectable by the user. A system built around a fast and simple design allowing deep state inspection and debugging; providing sufficient information for the users/developpers to customize the system to their liking.

I’m still planning on using the multiple return path function calls; after all this is one good way of speeding things up a bit while better managing various output states.

The dynamic relocation and the live upgrades are without timing guarantees; in fact, the entire system should probably not be real-time based; at best soft real-time. Let’s be honest, I do not have the team nor the inclination to go through official certification and make this into a commercial endeavour.

The allocated memory pages can then be shared with other processes for fast and efficient data transfer; when doing so the process sharing the memory page will receive a secret code that can be used to cancel the sharing and regain full control.  When shared, memory pages are in read-only mode for all users including the original process which shared the page.