From: jamal <hadi@cyberus.ca>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org, "" <netdev@oss.sgi.com>,
"" <linux-net@vger.kernel.org>
Subject: Re: anyone ever done multicast AF_UNIX sockets?
Date: Fri, 28 Feb 2003 08:33:48 -0500 (EST) [thread overview]
Message-ID: <20030228083009.Y53276@shell.cyberus.ca> (raw)
In-Reply-To: <3E5E7081.6020704@nortelnetworks.com>
On Thu, 27 Feb 2003, Chris Friesen wrote:
>
> 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.
>
I think this is a _very weak_ reason.
Without addressing any of your other arguements, can you describe what
such painful overhead you are talking about? Did you do any measurements
and under what circumstances are unix sockets vs say localhost bound
udp sockets are different? I am not looking for hand waving reason of
"but theres an IP stack".
cheers,
jamal
next prev parent reply other threads:[~2003-02-28 13:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 20:09 anyone ever done multicast AF_UNIX sockets? Chris Friesen
2003-02-27 22:21 ` Greg Daley
2003-02-28 13:33 ` jamal [this message]
2003-02-28 14:39 ` Chris Friesen
2003-03-01 3:18 ` jamal
2003-03-02 6:03 ` Chris Friesen
2003-03-02 14:11 ` jamal
2003-03-03 18:02 ` Chris Friesen
2003-03-03 12:51 ` Terje Eggestad
2003-03-03 12:35 ` David S. Miller
2003-03-03 17:09 ` Chris Friesen
2003-03-03 16:55 ` David S. Miller
2003-03-03 18:07 ` Chris Friesen
2003-03-03 17:56 ` David S. Miller
2003-03-03 19:11 ` Chris Friesen
2003-03-03 18:56 ` David S. Miller
2003-03-03 19:42 ` Terje Eggestad
2003-03-03 21:32 ` Chris Friesen
2003-03-03 23:38 ` Terje Eggestad
2003-03-03 19:39 ` Terje Eggestad
2003-03-03 22:29 ` Chris Friesen
2003-03-03 23:29 ` Terje Eggestad
2003-03-04 2:38 ` jamal
[not found] <3E5E7081.6020704@nortelnetworks.com.suse.lists.linux.kernel>
[not found] ` <20030228083009.Y53276@shell.cyberus.ca.suse.lists.linux.kernel>
[not found] ` <3E5F748E.2080605@nortelnetworks.com.suse.lists.linux.kernel>
[not found] ` <20030228212309.C57212@shell.cyberus.ca.suse.lists.linux.kernel>
[not found] ` <3E619E97.8010508@nortelnetworks.com.suse.lists.linux.kernel>
[not found] ` <20030302081916.S61365@shell.cyberus.ca.suse.lists.linux.kernel>
[not found] ` <3E6398C4.2020605@nortelnetworks.com.suse.lists.linux.kernel>
2003-03-03 18:18 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030228083009.Y53276@shell.cyberus.ca \
--to=hadi@cyberus.ca \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).