From: Josh Triplett <josh@joshtriplett.org>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Bus IPC
Date: Sat, 30 Jul 2016 15:21:00 -0700 [thread overview]
Message-ID: <20160730222100.6me2tt54w3e234wu@x> (raw)
In-Reply-To: <CANq1E4QvX6RMeapc8ZBRvg6UFdwCEbQMhgH=DqM6UZMkF3+T1g@mail.gmail.com>
On Fri, Jul 29, 2016 at 12:24:03AM +0200, David Herrmann wrote:
> Tom Gundersen and I would like to propose a technical session on
> in-kernel IPC systems. For roughly half a year now we have been
> developing (with others) a capability-based [1] IPC system for linux,
> called bus1 [2]. We would like to present bus1, start a discussion on
> open problems, and talk about the possible path forward for an upstream
> inclusion.
>
> While bus1 emerged out of the kdbus project, it is a new, independent
> project, designed from scratch.
I'd heard that the plan for bus1 was to provide DBus-compatible
semantics via a userspace compatibility layer. Do you still plan to do
that, so that current users of DBus can run on bus1 without
modification, or will current users of DBus need to port to bus1?
- Josh Triplett
next prev parent reply other threads:[~2016-07-30 22:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 22:24 David Herrmann
2016-07-28 22:57 ` Andy Lutomirski
2016-07-28 23:42 ` Jiri Kosina
2016-07-29 7:12 ` Hannes Reinecke
2016-07-30 22:25 ` Tom Gundersen
2016-07-29 2:41 ` Greg KH
2016-07-30 2:45 ` Steven Rostedt
2016-07-30 9:24 ` Arnd Bergmann
2016-07-30 21:58 ` Tom Gundersen
2016-07-30 22:21 ` Josh Triplett [this message]
2016-08-01 10:36 ` David Herrmann
2016-08-01 18:53 ` Josh Triplett
2016-08-02 8:43 ` Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160730222100.6me2tt54w3e234wu@x \
--to=josh@joshtriplett.org \
--cc=dh.herrmann@gmail.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox