From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: David Miller <davem@davemloft.net>,
rodrigo.moya@collabora.co.uk, javier@collabora.co.uk,
eric.dumazet@gmail.com, lennart@poettering.net,
kay.sievers@vrfy.org, alban.crequy@collabora.co.uk,
bart.cerneels@collabora.co.uk, sjoerd.simons@collabora.co.uk,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/10] af_unix: add multicast and filtering features to AF_UNIX
Date: Thu, 1 Mar 2012 14:57:51 +0200 [thread overview]
Message-ID: <CABBYNZJdYnZwm+Y15wdt225PhX=ApZrAbxH9da4EMrejWVmA1Q@mail.gmail.com> (raw)
In-Reply-To: <4F4F641E.7000501@collabora.co.uk>
Hi Javier,
On Thu, Mar 1, 2012 at 1:57 PM, Javier Martinez Canillas
<javier.martinez@collabora.co.uk> wrote:
> On 02/28/2012 08:05 PM, David Miller wrote:
>> From: Rodrigo Moya <rodrigo.moya@collabora.co.uk>
>> Date: Tue, 28 Feb 2012 11:47:39 +0100
>>
>>> Because of all of this, UDP/IP multicast wasn't even considered as an
>>> option. We might be wrong in some/all of those, so could you please
>>> comment on them to check if that's so?
>>
>> You guys seem to want something that isn't AF_UNIX, ordering guarentees
>> and whatnot, it really has no place in these protocols.
>>
>> You've designed a userlevel subsystem with requirements that no existing
>> socket layer can give, and you just figured you'd work that out later.
>>
>> I think you rather should have reconsidered these premises and designed
>> something that could handle reality which is AF_UNIX can't do multicast
>> and nobody guarentees those strange ordering requirements you seem to
>> have.
>
> Yes, you are right it doesn't follow AF_UNIX semantics so Unix sockets
> is not the best place to add our multicast implementation.
>
> So, now we are trying a different approach. To create a new address
> family AF_MCAST. That way we can have more control over the semantics of
> the socket interface for that family.
>
> We expect to have some patches in a few days and we will resend.
Lets say AF_MCAST is acceptable, wouldn't it make AF_UNIX obsolete?
>From what I can tell a lot, if not most, of users of AF_UNIX uses it
to implement some kind of IPC being it D-Bus, chromium or wayland and
eventually all of them run into the same problems. Actually the
article in lwn put it nice together: http://lwn.net/Articles/466304/
What about SCM_RIGHTS and other Ancillary Messages, would that be
acceptable in other socket families?
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2012-03-01 12:57 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 15:57 [PATCH 0/10] af_unix: add multicast and filtering features to AF_UNIX Javier Martinez Canillas
2012-02-20 15:57 ` [PATCH 01/10] af_unix: Documentation on multicast unix sockets Javier Martinez Canillas
2012-02-20 15:57 ` [PATCH 02/10] af_unix: Add constant for unix socket options level Javier Martinez Canillas
2012-02-20 15:57 ` [PATCH 03/10] af_unix: add setsockopt on unix sockets Javier Martinez Canillas
2012-02-20 16:20 ` David Miller
2012-02-20 19:13 ` [PATCH 0/10] af_unix: add multicast and filtering features to AF_UNIX Colin Walters
2012-02-21 8:07 ` Rodrigo Moya
2012-02-24 20:36 ` David Miller
2012-02-27 14:00 ` Javier Martinez Canillas
2012-02-27 19:05 ` David Miller
2012-02-28 10:47 ` Rodrigo Moya
2012-02-28 14:28 ` David Lamparter
2012-02-28 15:24 ` Javier Martinez Canillas
2012-02-28 16:33 ` Javier Martinez Canillas
2012-02-28 19:05 ` David Miller
2012-03-01 11:57 ` Javier Martinez Canillas
2012-03-01 12:26 ` Eric Dumazet
2012-03-01 12:33 ` David Laight
2012-03-01 12:50 ` Rodrigo Moya
2012-03-01 12:59 ` Eric Dumazet
2012-03-01 13:56 ` Javier Martinez Canillas
2012-03-01 16:00 ` Eric Dumazet
2012-03-01 16:02 ` Luiz Augusto von Dentz
2012-03-01 17:06 ` Javier Martinez Canillas
2012-03-01 17:59 ` Eric Dumazet
2012-03-01 18:10 ` Alan Cox
2012-03-01 19:02 ` Javier Martinez Canillas
2012-03-01 19:29 ` Javier Martinez Canillas
2012-03-01 18:53 ` David Dillow
2012-03-01 20:55 ` David Miller
2012-03-02 4:40 ` Stephen Hemminger
2012-03-01 20:44 ` David Miller
2012-03-01 22:01 ` Luiz Augusto von Dentz
2012-03-01 22:08 ` David Miller
2012-03-02 8:39 ` Luiz Augusto von Dentz
2012-03-02 8:55 ` David Miller
2012-03-02 9:27 ` Javier Martinez Canillas
2012-03-02 9:39 ` David Miller
2012-03-02 13:13 ` Eric Dumazet
2012-03-02 16:34 ` Javier Martinez Canillas
2012-03-02 17:08 ` Alan Cox
2012-03-05 8:38 ` Luiz Augusto von Dentz
2012-03-05 14:05 ` Martin Mares
2012-03-05 15:11 ` Javier Martinez Canillas
2012-03-05 15:49 ` Martin Mares
2012-03-05 18:55 ` David Lamparter
2012-03-02 10:08 ` Luiz Augusto von Dentz
2012-03-03 12:20 ` Martin Mares
2012-03-02 22:19 ` david
2012-03-01 12:57 ` Luiz Augusto von Dentz [this message]
2012-03-01 20:42 ` David Miller
2012-03-01 14:25 Erik Hugne
2012-03-01 17:18 ` Rodrigo Moya
2012-03-02 7:01 ` Ying Xue
[not found] ` <4F506ABC.8050807@windriver.com>
2012-03-05 15:49 ` Erik Hugne
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='CABBYNZJdYnZwm+Y15wdt225PhX=ApZrAbxH9da4EMrejWVmA1Q@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=alban.crequy@collabora.co.uk \
--cc=bart.cerneels@collabora.co.uk \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=javier.martinez@collabora.co.uk \
--cc=javier@collabora.co.uk \
--cc=kay.sievers@vrfy.org \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rodrigo.moya@collabora.co.uk \
--cc=sjoerd.simons@collabora.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).