[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrWrxc8foPYbRPtxwNX0sHK_=vLFLDXXyXu+2U2=B+=qCQ@mail.gmail.com>
Date: Wed, 29 Oct 2014 15:15:51 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Linux API <linux-api@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
John Stultz <john.stultz@...aro.org>,
Arnd Bergmann <arnd@...db.de>, Tejun Heo <tj@...nel.org>,
Marcel Holtmann <marcel@...tmann.org>,
Ryan Lortie <desrt@...rt.ca>,
Bastien Nocera <hadess@...ess.net>,
David Herrmann <dh.herrmann@...il.com>,
Djalal Harouni <tixxdz@...ndz.org>,
simon.mcvittie@...labora.co.uk, daniel@...que.org,
alban.crequy@...labora.co.uk, javier.martinez@...labora.co.uk,
Tom Gundersen <teg@...m.no>
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@...uxfoundation.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists