Hi everyone, I recently discovered HelenOS and was very happy to see its design philosophy and approach! I am a big fan of your principles: a truly decoupled design, breaking with POSIX, and the "breadth first" design approach.
One thing I was curious about as I started studying its design: why put async IPC in the kernel? My impression was that one of L4's major innovations was putting only synchronous IPC in the kernel, which simplifies the kernel and increases performance. Async IPC sounds like a more Mach-like design, with associated problems of queuing. Can't async IPC/queueing be implemented in user-space on top of a kernel-based sync IPC? I know you have spent a lot of time refining the design, so I'm curious to know what made you decide on an async approach. Best, Josh
_______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
