From: jlnance@unity.ncsu.edu
To: linux-kernel@vger.kernel.org
Subject: sendfile or r+w for sending file to multiple machines
Date: Fri, 28 Mar 2003 09:23:28 -0500 [thread overview]
Message-ID: <20030328142328.GA5242@ncsu.edu> (raw)
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.
We could also write this using sendfile, and I dont know if that
is a good idea or not (hence this post). I think I would have to start
multiple threads to get sendfile to work. This makes things more
complex which is a minus, but how about performance. Do you think
this would work better than read+write? The files are larger than
system memory so our goal is to avoid reading the multiple times.
With sendfile we can not really control how the files get read, but
it seems likely that the different threads would inherently synchronize
themselves. Any thoughts?
Thanks,
Jim
next reply other threads:[~2003-03-28 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 14:23 jlnance [this message]
2003-03-28 15:02 ` sendfile or r+w for sending file to multiple machines Chris Friesen
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=20030328142328.GA5242@ncsu.edu \
--to=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.