Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760221AbcJ1NLE (ORCPT ); Fri, 28 Oct 2016 09:11:04 -0400 Received: from mail-oi0-f66.google.com ([209.85.218.66]:35856 "EHLO mail-oi0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757923AbcJ1NLC (ORCPT ); Fri, 28 Oct 2016 09:11:02 -0400 MIME-Version: 1.0 In-Reply-To: <20161026191810.12275-1-dh.herrmann@gmail.com> References: <20161026191810.12275-1-dh.herrmann@gmail.com> From: Richard Weinberger Date: Fri, 28 Oct 2016 15:11:00 +0200 Message-ID: Subject: Re: [RFC v1 00/14] Bus1 Kernel Message Bus To: David Herrmann Cc: LKML , Andy Lutomirski , Jiri Kosina , Greg KH , Hannes Reinecke , Steven Rostedt , Arnd Bergmann , Tom Gundersen , Josh Triplett , Linus Torvalds , Andrew Morton Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 811 Lines: 19 On Wed, Oct 26, 2016 at 9:17 PM, David Herrmann 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. -- Thanks, //richard