The constructor is the basic mechanism for creating new program instances in EROS. It performs the logical equivalent of POSIX fork+exec. In addition, it provides some security assertions about the resulting process.

This slide isn't the one that I used in the original talk -- this one is more explicit about where all the work is going. When you look at the process creation benchmark, take a moment to flip back here and see what is going on to fabricate a process.

The ``multiple IPCs'' label is trying to indicate that there is a copy-on-write action for every page in the new address spaces working set. Many of these pages have to get allocated before the new service instance can return to the client.

Obviously, EROS is highly process intensive.