public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "A.D.F." <adefacc@tin.it>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TCP Zero Copy for mmapped files
Date: Sat, 04 Jan 2003 13:10:02 +0000	[thread overview]
Message-ID: <3E16DD2A.2BCDE86B@tin.it> (raw)
In-Reply-To: 20030104004153.GA16238@werewolf.able.es

"J.A. Magallon" wrote:
> 
> On 2003.01.04 A.D.F. wrote:
> > 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.
> >
> 
> Apache2 uses mmap() to open files ??

No, you cannot use mmap() to open files ... :-),
at most mmap() helps caching static file contents in order
to avoid too many open() / close() calls (which maybe slow).

Apache 2 seems to use sendfile (in blocking mode) by default,
it uses mmap() only if you enable it (see also mod_file_cache).

Other web servers (i.e. Zeus) use widely mmap() for specific
file sizes, when it is usually a strong win (specially under *BSD and
Solaris)
in big / busy servers with lots of RAM.

> So then there is a reason to include it in my patchset...

Certainly yes (after required bug fixes :-)

-- 
Nick Name:      A.D.F.
E-Mail:         adefacc@tin.it
E-Mail-Font:    Courier New (plain text, no html)
--

      parent reply	other threads:[~2003-01-04 12:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 23:34 TCP Zero Copy for mmapped files A.D.F.
2003-01-04  0:41 ` J.A. Magallon
2003-01-04  1:53   ` dean gaudet
2003-01-04 13:10   ` A.D.F. [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=3E16DD2A.2BCDE86B@tin.it \
    --to=adefacc@tin.it \
    --cc=jamagallon@able.es \
    --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