[lkml]   [2012]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 0/10] af_unix: add multicast and filtering features to AF_UNIX

    On 02/24/2012 09:36 PM, David Miller wrote:
    > My first impression is that I'm amazed at how much complicated new
    > code you have to add to support groups of receivers of AF_UNIX
    > messages.
    > I can't see how this is better than doing multicast over ipv4 using
    > UDP or something like that, code which we have already and has been
    > tested for decades.

    Primary for performance reasons. D-bus is an IPC system for processes in
    the same machine so traversing the whole TCP/IP stack seems a little
    overkill to me. We will try it though to have numbers on the actual
    overhead of using UDP multicast over IP instead of multicast Unix domain

    We also thought of using Netlink sockets since it already supports
    multicast and should be more lightweight than IP multicast. But even
    Netlink doesn't meet our needs since our multicast on Unix sockets
    implementation has different semantics needed for D-bus:

    - total order is guaranteed: If sender A sends a message before B, then
    receiver C and D should both get message A first and then B.

    - slow readers: dropping packets vs blocking the sender. Although
    datagrams are not reliable on IP, datagrams on Unix sockets are never
    lost. So if one receiver has its buffer full the sender is blocked
    instead of dropping packets. That way we guarantee a reliable
    communication channel.

    - multicast group acess control: controlling who can join the multicast

    - multicast on loopback is not supported: which means we have to use a
    NIC (i.e: eth0).

    > I really don't want to apply this stuff, it looks bloated,
    > complicated, and there is another avenue for doing what you want to
    > do.

    We can work to reduce the implementation complexity and make it less

    Or you don't like the idea in general?

    > Applications have to change to support the new multicast facilities,
    > so they can equally be changed to use a real transport that already
    > supports multicasting.

    Yes, this is not about minimizing user-space application change but to
    improve the D-bus performance, or any other framework that relies on
    multicast communication on a single machine.

    Best regards,

     \ /
      Last update: 2012-02-27 15:01    [W:0.029 / U:6.904 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site