From: Hannes Reinecke <hare@suse.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Bus IPC
Date: Fri, 29 Jul 2016 09:12:40 +0200 [thread overview]
Message-ID: <668b998d-ffa6-ae7d-8782-903db550a514@suse.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1607290140040.24757@cbobk.fhfr.pm>
On 07/29/2016 01:42 AM, Jiri Kosina wrote:
> On Fri, 29 Jul 2016, David Herrmann wrote:
>
> [ .. snip .. ]
>> Everyone interested in IPC is invited to the discussion. In particular,
>> we would welcome everyone who participated in the Binder and kdbus
>> discussions, is involed in shmem+memcg (or other bus1-related
>> subsystems), possibly including:
>>
>> o Andy Lutomirski
>> o Greg Kroah-Hartman
>> o Steven Rostedt
>> o Eric W. Biederman
>> o Jiri Kosina
>
> I'd definitely be very interested in participating in such a discussion,
> should it happen at KS or whereever else.
>
> Please put me to the "I still don't fully understand why teaching AF_UNIX
> about multicast shouldn't do the job" discussion group :)
>
Oh.
_That_ topic would definitely interest me, too.
Not so much from the obvious kdbus/binder/<insert your favourite topic
here> type of thing, but because I'm still struggling to find a way of
passing information from one side of the kernel to the other.
notifier_chains simply don't fit the bill here.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.com +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-07-29 7:12 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 [this message]
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
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=668b998d-ffa6-ae7d-8782-903db550a514@suse.com \
--to=hare@suse.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