|| ||Chris Friesen <chris.friesen-AT-genband.com> |
|| ||David Miller <davem-AT-davemloft.net> |
|| ||Re: AF_BUS socket address family |
|| ||Sun, 01 Jul 2012 22:49:06 -0600|
|| ||vincent.sanders-AT-collabora.co.uk, netdev-AT-vger.kernel.org,
|| ||Article, Thread
On 06/29/2012 05:18 PM, David Miller wrote:
> From: Vincent Sanders<firstname.lastname@example.org>
> Date: Sat, 30 Jun 2012 00:12:37 +0100
>> I had hoped you would have at least read the opening list where I
>> outlined the underlying features which explain why none of the
>> existing IPC match the requirements.
> I had hoped that you had read the part we told you last time where
> we explained why multicast and "reliable delivery" are fundamentally
> incompatible attributes.
> We are not creating a full address family in the kernel which exists
> for one, and only one, specific and difficult user.
For what it's worth, the company I work for (and a number of other
companies) currently use an out-of-tree datagram multicast messaging
protocol family based on AF_UNIX.
If AF_BUS were to be accepted, it would be essentially trivial for us to
port our existing userspace messaging library to use it instead of our
current protocol family, and we would almost certainly do so.
I'd love to see AF_BUS go in.
to post comments)