From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: RE: [PATCH 0/10] af_unix: add multicast and filtering features to AF_UNIX Date: Thu, 01 Mar 2012 04:59:35 -0800 Message-ID: <1330606775.2465.56.camel@edumazet-laptop> References: <1330606237.27405.5.camel@megeve> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: David Laight , Javier Martinez Canillas , David Miller , javier@collabora.co.uk, 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 To: Rodrigo Moya Return-path: In-Reply-To: <1330606237.27405.5.camel@megeve> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Le jeudi 01 mars 2012 =C3=A0 13:50 +0100, Rodrigo Moya a =C3=A9crit : > the main problem in D-Bus we are trying to solve is the context > switches, since right now, there is a daemon, which listens on a UNIX > socket, and all traffic in the bus goes through it, and then the daem= on > has to route the messages it gets on that socket to the corresponding > place(s). So, every time someone sends a message to D-Bus, since all > traffic goes through the daemon, dbus-daemon gets waked-up, which is = one > of the biggest bottlenecks we are trying to fix. >=20 > That's why we are thinking about using multicast with socket filters,= so > that the daemon only gets traffic it cares about and thus is not wake= d > up and context switches don't happen when not needed. >=20 > Using message queues, AFAICS, we would have the same problem, as the > daemon would create the message queue and would get all traffic, righ= t? >=20 This is why I mentioned extensions. Anyway, if you think multicast sockets is the way to go, then you could setup a virtual network just to be able to use AF_INET multicast. Thats probably doable without kernel patching.