Re: vk_l4 -- CVS Setup

[Debian UserAd Buijsen]

>> Reading the L4 definition, the IPC mechanisms seem very specific to
>> machines with some sort of shared address space access. It think it
>> would be very difficult to extend the idea of network transparency to L4
>> without destroying it's simplicity. L4 is already doing a number of
>> memory tricks to keep context switching cheap between it's threads,
>> using segment registers and such, where possible.
>> 
>> Network transparent RPC definitely seems like a userspace candidate to
>> me. The RPC you are describing would be built as messages to some sort
>> of RPC server (L4 server) making use of the L4 ipc calls to communicate
>> the message to the server. All concepts of networking and such would be
>> strictly outside of the L4 kernel.
>> 
>> -- Ian

Version 2 of the L4 spec. has Unique IDs containing a "site" field, so 
kernel-assisted
remote IPC was considered at a time, I presume.  A "site-fault" for non-local 
IPC would be
one method to handle it, or a generalized form of IPC redirection.

  Ad