linux-kernel - Re: New Address Family: Inter Process Networking (IPN)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <47585D66.3000404@nortel.com>
Date:	Thu, 06 Dec 2007 14:36:54 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Renzo Davoli <renzo@...unibo.it>, linux-kernel@...r.kernel.org
Subject: Re: New Address Family: Inter Process Networking (IPN)

Andi Kleen wrote:
>>"This document describes Linux Netlink, which is used in Linux both as
>>   an intra-kernel messaging system as well as between kernel and user
>>   space."
> 
> 
> It can be used between user space daemons as well. In fact it is.
> e.g. they often listen to each other's messages.

One problem we ran into was that there are only 32 multicast groups per 
netlink protocol family.

We had a situation where we could have used netlink, but we needed the 
equivalent of thousands of multicast groups.  Latency was very 
important, so we ended up doing essentially a multicast unix socket 
rather than taking the extra penalty for UDP multicast.

Chris
--
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/