[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1330622294.5373.8.camel@megeve>
Date: Thu, 01 Mar 2012 18:18:14 +0100
From: Rodrigo Moya <rodrigo.moya@...labora.co.uk>
To: Erik Hugne <erik.hugne@...csson.com>
Cc: "netdev-owner@...r.kernel.org" <netdev-owner@...r.kernel.org>,
"David.Laight@...LAB.COM" <David.Laight@...LAB.COM>,
"davem@...emloft.net" <davem@...emloft.net>,
"javier@...labora.co.uk" <javier@...labora.co.uk>,
"lennart@...ttering.net" <lennart@...ttering.net>,
"kay.sievers@...y.org" <kay.sievers@...y.org>,
"alban.crequy@...labora.co.uk" <alban.crequy@...labora.co.uk>,
"bart.cerneels@...labora.co.uk" <bart.cerneels@...labora.co.uk>,
"sjoerd.simons@...labora.co.uk" <sjoerd.simons@...labora.co.uk>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"eric.dumazet@...il.com" <eric.dumazet@...il.com>
Subject: Re: [PATCH 0/10] af_unix: add multicast and filtering features to
AF_UNIX
Hi Erik
On Thu, 2012-03-01 at 15:25 +0100, Erik Hugne wrote:
> Hi
> Have you considered using TIPC instead?
> It already provides multicast messaging with guaranteed ordering, and reliable delivery (SOCK _RDM)
>
I didn't know about TIPC, so have been having a quick look over it, and
have some questions about it:
* since it's for cluster use, I guess it's based on AF_INET sockets? if
so, see the messages from Luis Augusto and Javier about this breaking
current D-Bus apps, that use fd passing, for out-of-band data
* D-Bus works locally, with all processes on the same machine, but there
are 2 buses (daemons), one for system-related interfaces, and one per
user, so how would this work with TIPC. Can you create several
clusters/networks (as in TIPC addressing semantics) on the same machine
on the loopback device?
* I installed tipcutils on my machine, and it asked me if I wanted to
setup the machine as a TIPC node. Does this mean every machine needs to
be setup as a TIPC node before any app makes use of it? That is, can I
just create a AF_TIPC socket on this machine and just make it work
without any further setup?
* I guess it is easy to prevent any TIPC-enabled machine to get into the
local communication channel, right? That is, what's the security
mechanism for allowing local-only communications?
I'll stop asking questions and have a deeper look at it :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists