Re: Lightweight virtualization - the rump approach

[Jean-Yves Migeon <jeanyves.migeon%free.fr@localhost>]

On Mon, 17 May 2010 13:16:13 +0300, Antti Kantee <pooka%cs.hut.fi@localhost> 
wrote:
> On Mon May 17 2010 at 12:02:36 +0200, Jean-Yves Migeon wrote:
>> I am probably missing something then; p2k being a translation layer, it
>> is
>> shared between the different rump_* parts. As such, I considered
>> (wrongfully maybe?) that the interface/protocol communication is not
>> expected to change with regards to rump_* components. Which means that
>> having rump_somefs support is a matter of making its code run in
>> userland,
>> and talk with the kernel through p2k (which remains untouched in this
>> case).
> 
> p2k uses syscalls/vnodeops to talk with the kernel file servers.  So
both
> p2k and the kernel code remain unchanged.
> 
> But you still need to *mount* the file system.  That's what the
> rump_somefs utility is all about (and likewise mount_somefs).  Have a
look
> at the code and the fourth argument to mount(2) and you'll understand.

Many thanks for answering my questions, Antti. Now that I have sane (and
safe) pointers, I have some readings to do.

Cheers!

-- 
Jean-Yves Migeon
jeanyves.migeon%free.fr@localhost