Re: AF_BUS socket address family

From
David Miller <davem@davemloft.net>
Date
2012-07-01 21:45:48
Also in
lkml
Reply to
Alan Cox, 2012-07-01
From: Alan Cox <redacted>
Date: Sun, 1 Jul 2012 15:16:59 +0100
quoted
The issue is that what to do when a receiver goes deaf is a policy
issue.
Something all these protocols alredy recognize and have done for years.
The real issue for AF_BUS versus the current slow AF_UNIX approach is
that you really need to know *who* is blocked up.

That's no different to UDP multicast and needing to know how errored the
frame.
And the policy on what to do about such UDP multicast errors is in
userspace, which is precisely my point.
Thread (50 messages) 50 messages, 17 authors, last reply 2012-07-09
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help