On 25/10/14 12:51, Justin Cormack wrote:
>> So just in case the above was hard-to-read, _A DIAGRAM_:
>>
>> PF_INET:
>> app -> syscall -> socket -> netinet -> interface -> hypercall or hw
>> PF_HOST:
>> app -> syscall -> socket -> sockin/host -> hypercall (host socket)
>>
>> I'd still call that an expert scenario ;)
>
> He just wanted PF_UNIX to be host in effect, ie a host replacement for
> that socket family. I can see quite a lot of rump programs where this
> might be useful, as most programs dont use ipc between threads.
> Obviously it might not support sending fds or credentials, and you
> would not have an easy way to unlink a named socket, but might still
> work ok.
Ok, then it's even easier, since you can just hook up PF_UNIX to sockin
(PF_UNIX is normally provided by rumpnet_local, i.e. not a part of
rumpnet_netinet{,6}).
As an aside, by default rumphijack handles PF_UNIX sockets as host
calls. The reason for this choice was to make X clients work by default ;)
------------------------------------------------------------------------------
_______________________________________________
rumpkernel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
