From: Chris Friesen <cfriesen@nortelnetworks.com>
To: jlnance@unity.ncsu.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: sendfile or r+w for sending file to multiple machines
Date: Fri, 28 Mar 2003 10:02:40 -0500 [thread overview]
Message-ID: <3E846410.90804@nortelnetworks.com> (raw)
In-Reply-To: 20030328142328.GA5242@ncsu.edu
jlnance@unity.ncsu.edu wrote:
> Hello All,
> I have an application that needs to be able to send large files to
> multiple machines (less than 10). The files get sent to the machines at
> the same time so we are thinking about writing the code so that it does
> 1 read (or perhaps a mmap) on the file, and then does multiple writes,
> onece to each machines socket.
> We are also considering using multicast but this seems unnecessarily
> complex. I dont want to reimplement TCP.
Given that your stated goal is to minimize disk reads, to me at least reading
once and sending via TCP on multiple sockets seems to make sense, and is the
only option that actually gives you direct control over the reads.
If it was an advantage for the receivers to have the file as soon as possible,
you might be able to do slightly better by sending the whole file once as UDP to
all listeners and then filling in the blanks later. This way, some of the
listeners would get the file on the first pass and not have to wait for the
lowest common denominator. You probably wouldn't gain much though.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
prev parent reply other threads:[~2003-03-28 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 14:23 sendfile or r+w for sending file to multiple machines jlnance
2003-03-28 15:02 ` Chris Friesen [this message]
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=3E846410.90804@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=jlnance@unity.ncsu.edu \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.