| To: | linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx |
|---|---|
| Subject: | anyone ever done multicast AF_UNIX sockets? |
| From: | Chris Friesen <cfriesen@xxxxxxxxxxxxxxxxxx> |
| Date: | Thu, 27 Feb 2003 15:09:37 -0500 |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204 |
|
It is fairly common to want to distribute information between a single sender and multiple receivers on a single box. Multicast IP sockets are one possibility, but then you have additional overhead in the IP stack. Unix sockets are more efficient and give notification if the listener is not present, but the problem then becomes that you must do one syscall for each listener. So, here's my main point--has anyone ever considered the concept of multicast AF_UNIX sockets? The main features would be: --ability to associate/disassociate a socket with a multicast address --ability to associate/disassociate with all multicast addresses (possibly through some kind of raw socket thing, or maybe a simple wildcard multicast address) --on process death all sockets owned by that process are disassociated from any multicast addresses that they were associated with --on sending a packet to a multicast address and there are no sockets associated with it, return -1 with errno=ECONNREFUSED The association/disassociation could be done using the setsockopt() calls the same as with udp sockets, everything else would be the same from a userspace perspective. Any thoughts? How hard would this be to put in? Chris
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | linux_mib docs?, Randy.Dunlap |
|---|---|
| Next by Date: | Re: linux_mib docs?, Andi Kleen |
| Previous by Thread: | linux_mib docs?, Randy.Dunlap |
| Next by Thread: | Re: anyone ever done multicast AF_UNIX sockets?, Greg Daley |
| Indexes: | [Date] [Thread] [Top] [All Lists] |