User Details
- User Since
- Mon, Nov 16, 7:40 AM (2 d, 11 h)
Today
I first encountered Doors in illumos/OmniOS. I liked the simplicity of writing client/server code without building the request/reply synchronization machinery myself. The scheduler handoff was particularly interesting: the caller yields execution directly to the server, reducing synchronous round-trip latency. Using Doors across Solaris/illumos zones also seemed useful.
Thank you. I'd be interested to see how this fits CheriBSD co-processes.
There is a similar goal of splitting an application into cooperating processes, but the virtual memory model differs. Here, processes retain separate address spaces and explicitly map selected Door SHM regions with defined access rights. Shared regions do not need to have the same virtual address in each process.
The multiplexed syscall came from the original ioctl-based implementation. I understand the compatibility and tracing concerns. My hesitation about separate syscalls is that Doors has many operations, and exposing each one would considerably expand the syscall surface. I'll fix the pointer argument types and add libsysdecode support. As for the syscall layout, I think this is worth discussing further and weighing the advantages and disadvantages of both approaches before deciding.
