Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1760770AbcJ1Nh5 (ORCPT <rfc822;w@1wt.eu>);
        Fri, 28 Oct 2016 09:37:57 -0400
Received: from mail-vk0-f67.google.com ([209.85.213.67]:32863 "EHLO
        mail-vk0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1760433AbcJ1Nh4 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 28 Oct 2016 09:37:56 -0400
MIME-Version: 1.0
X-Originating-IP: [2a02:fe0:c130:1430:7e7a:91ff:fe0e:3e2c]
In-Reply-To: <CAFLxGvyFyd2APT4W16CA1R0tYmneMZ5sUW1q3pc1b8-hFQJe1w@mail.gmail.com>
References: <20161026191810.12275-1-dh.herrmann@gmail.com> <CAFLxGvyFyd2APT4W16CA1R0tYmneMZ5sUW1q3pc1b8-hFQJe1w@mail.gmail.com>
From: Tom Gundersen <teg@jklm.no>
Date: Fri, 28 Oct 2016 15:37:34 +0200
Message-ID: <CAG-2HqWUjLLO6g75qQr0Ym6JLUNssHOoWN=Hb0mUuCJRrogk-Q@mail.gmail.com>
Subject: Re: [RFC v1 00/14] Bus1 Kernel Message Bus
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: David Herrmann <dh.herrmann@gmail.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Andy Lutomirski <luto@amacapital.net>, Jiri Kosina <jikos@kernel.org>,
        Greg KH <greg@kroah.com>, Hannes Reinecke <hare@suse.com>,
        Steven Rostedt <rostedt@goodmis.org>, Arnd Bergmann <arnd@arndb.de>,
        Josh Triplett <josh@joshtriplett.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Andrew Morton <akpm@linux-foundation.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1080
Lines: 25

On Fri, Oct 28, 2016 at 3:11 PM, Richard Weinberger
<richard.weinberger@gmail.com> wrote:
> On Wed, Oct 26, 2016 at 9:17 PM, David Herrmann <dh.herrmann@gmail.com> wrote:
>> Hi
>>
>> This proposal introduces bus1.ko, a kernel messaging bus. This is not a request
>> for inclusion, yet. It is rather an initial draft and a Request For Comments.
>>
>> While bus1 emerged out of the kdbus project, bus1 was started from scratch and
>> the concepts have little in common. In a nutshell, bus1 provides a
>> capability-based IPC system, similar in nature to Android Binder, Cap'n Proto,
>> and seL4. The module is completely generic and does neither require nor mandate
>> a user-space counter-part.
>
> One thing which is not so clear to me is the role of bus1 wrt. containers.
> Can a container A exchange messages with a container B?
> If not, where is the boundary? I guess it is the pid namespace.

There is no restriction with respect to containers. The metadata is
translated between namespaces, obviously, but you can send messages to
anyone you have a handle to.

Cheers,

Tom