Re: [PATCH 00/12] Add kdbus implementation

On Wed, Oct 29, 2014 at 3:27 PM, Greg Kroah-Hartman
[off-list ref] wrote:

On Wed, Oct 29, 2014 at 03:15:51PM -0700, Andy Lutomirski wrote:

quoted

(reply 1/2 -- I'm replying twice to keep the threading sane)

On Wed, Oct 29, 2014 at 3:00 PM, Greg Kroah-Hartman
[off-list ref] wrote:

quoted

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.

quoted

 * 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?

See the document for the details.

quoted

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?

Yes.

Why?  Aren't they completely isolated?  Confused.

quoted

What's "container-name"?

Is that used in the documentation?

/dev/kdbus/domain/<container-name>/+ directory shows up inside the
domain as /dev/kdbus/.

I guess that's the thing that the creator requests.

--Andy

quoted

Given that domains have random IDs, how can they be checkpointed and restored?

Good question, I don't know about checkpoint/restore, but I think that
has been done.  Daniel would know more than I do about that.

thanks,

greg k-h

-- 
Andy Lutomirski
AMA Capital Management, LLC