From: "A.D.F." <adefacc@tin.it>
To: linux-kernel@vger.kernel.org
Subject: TCP Zero Copy for mmapped files
Date: Fri, 03 Jan 2003 23:34:21 +0000 [thread overview]
Message-ID: <3E161DFD.AB8D25AE@tin.it> (raw)
FreeBSD 5.0 should already have a zero copy for mmapped files and
IMHO it would be worth to have it in Linux 2.6 too.
It would also be very nice to be able to enable zero copy for mmapped files
by a config option.
Many applications use mapped memory to serve lots of small and
medium sized files (4 - 1024 KB) or even a few big files
(think at web servers, i.e. Apache 2, etc.); this is done to better
serve multiple / parallel downloads being done on the same files.
Using or not using mmap() is a userland / application choice that depends
on lots of factors / strategies that are outside kernel scope.
Besides this there seems to be some work in progress to speed up
mmap() calls, thus why not doing all the work right ?
--
Nick Name: A.D.F.
E-Mail: adefacc@tin.it
E-Mail-Font: Courier New (plain text, no html)
--
next reply other threads:[~2003-01-03 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 23:34 A.D.F. [this message]
2003-01-04 0:41 ` TCP Zero Copy for mmapped files J.A. Magallon
2003-01-04 1:53 ` dean gaudet
2003-01-04 13:10 ` A.D.F.
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=3E161DFD.AB8D25AE@tin.it \
--to=adefacc@tin.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox