From: Tom Gundersen <teg@jklm.no>
To: Arnd Bergmann <arnd@arndb.de>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Bus IPC
Date: Sat, 30 Jul 2016 23:58:41 +0200 [thread overview]
Message-ID: <CAG-2HqU4oro52=GEY5tUwisX-hoUCUQZF=+e-VhaePjVMSm18g@mail.gmail.com> (raw)
In-Reply-To: <1519332.ZM9tMjbubR@wuerfel>
Hi Arnd,
On Sat, Jul 30, 2016 at 11:24 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Friday, July 29, 2016 12:24:03 AM CEST 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.
l...]
> I'd like to join in discussing the user interface. The current version
> seems (compared to kdbus) simple enough that we could consider using
> syscalls instead of a miscdev.
Yeah, using syscalls would probably make the most sense if and when we
submit it upstream. The only reason we didn't so far was that it has
been easier to develop it out-of-tree as a module.
Cheers,
Tom
next prev parent reply other threads:[~2016-07-30 21:59 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 [this message]
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
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='CAG-2HqU4oro52=GEY5tUwisX-hoUCUQZF=+e-VhaePjVMSm18g@mail.gmail.com' \
--to=teg@jklm.no \
--cc=arnd@arndb.de \
--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