| From | Tom Gundersen <> | Date | Fri, 28 Oct 2016 15:37:34 +0200 | Subject | Re: [RFC v1 00/14] Bus1 Kernel Message Bus |
| |
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
|