Looks horribly inefficient to me (as opposed to what they claim). I am
unconvinced that a "message-passing interface" to device driver/OS
interaction can provide "high-performance I/O systems." Why stick
what essentially amounts to another protocol stack sandwiched between
the hardware-specific points and the O/S layer? Eesh.
The only slightly cool thing that could arise out of this would be a
truly heterogeneous multiprocessor; with a little extension, one machine
could call OS services on another machine via the protocol layer. This
might be desirable for distributed-memory systems except for the fact that one
bad kernel call could bring down all the machines in the cluster.
-- "Honestly, it's like shooting | Bob Glamm H: +1 612 6239437 W: +1 612 6268981 fish in a barrel. Twice. With | URL: http://www-mount.ee.umn.edu/~glamm an elephant gun. At point +----------------------------------------------- blank range. In the head." -- from the BOFH files, part 6