Messages in this thread | | | From | Andy Lutomirski <> | Date | Wed, 29 Oct 2014 15:15:51 -0700 | Subject | Re: [PATCH 00/12] Add kdbus implementation |
| |
(reply 1/2 -- I'm replying twice to keep the threading sane)
On Wed, Oct 29, 2014 at 3:00 PM, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote: > kdbus is a kernel-level IPC implementation that aims for resemblance to > the the protocol layer with the existing userspace D-Bus daemon while > enabling some features that couldn't be implemented before in userspace. >
> * Support for multiple domains, completely separated from each other, > allowing multiple virtualized instances to be used at the same time.
Given that there is no such thing as a device namespace, how does this work?
The docs seem a bit confusing to me as to whether there's a hierarchy of domains. Do domains have a concept of a parent?
What's "container-name"?
Given that domains have random IDs, how can they be checkpointed and restored?
--Andy
| |