All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.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: Tue, 2 Aug 2016 10:43:31 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1608021033200.22028@cbobk.fhfr.pm> (raw)
In-Reply-To: <CANq1E4QvX6RMeapc8ZBRvg6UFdwCEbQMhgH=DqM6UZMkF3+T1g@mail.gmail.com>

On Fri, 29 Jul 2016, David Herrmann wrote:

> While bus1 emerged out of the kdbus project, it is a new, independent
> project, designed from scratch. Its main goal is to implement an n-to-n
> communication bus on linux. A lot of inspiration is taken from both
> DBus, as well as the the most commonly used IPC systems of other OSs,
> and related research projects (including Android Binder, OS-X/Hurd Mach
> IPC, Solaris Doors, Microsoft Midori IPC, seL4, Sandstorm's Cap'n'Proto,
> ..).
[ ... ]
>  o Andy Lutomirski
>  o Greg Kroah-Hartman
>  o Steven Rostedt
>  o Eric W. Biederman
>  o Jiri Kosina

So I've given dbus1 a cursory look, and I fully agree that this would be 
an excellent topic; most importantly to make sure that maintainers who 
have been involved in previous kdbus discussions / reviews get an overview 
that this is indeed substantially different (and how exactly), and throw 
away any prejudice they might have gathered in the previous review rounds.

Thanks,

-- 
Jiri Kosina
SUSE Labs

      parent reply	other threads:[~2016-08-02  8:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28 22:24 [Ksummit-discuss] [TECH TOPIC] Bus IPC 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
2016-08-01 10:36   ` David Herrmann
2016-08-01 18:53     ` Josh Triplett
2016-08-02  8:43 ` Jiri Kosina [this message]

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=alpine.LNX.2.00.1608021033200.22028@cbobk.fhfr.pm \
    --to=jikos@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.