From: "David S. Miller" <davem@redhat.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Thomas Ogrisegg <tom@rhadamanthys.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] TCP Zero Copy for mmapped files
Date: 01 Jan 2003 22:37:01 -0800 [thread overview]
Message-ID: <1041489421.3703.6.camel@rth.ninka.net> (raw)
In-Reply-To: <20021230012937.GC5156@work.bitmover.com>
On Sun, 2002-12-29 at 17:29, Larry McVoy wrote:
> How about putting this into a different function? It's a lot to add
> inline for a special case.
This patch also has a ton of other problems:
1) Does not handle writes that straddle multiple VMAs
2) We do not want to encourage people to use this mmap
scheme anyways. The mmap way consumes precious VM
space, whereas the sendfile scheme does not.
3) Finally, I'm very dubious about the "this is faster than
TUX claim". Firstly because you've not provided your
self-made HTTP server so that others can try to reproduce
your benchmark. And secondly because you haven't indicated
if your self-made HTTP server is as full featured as TUX or
not. And thirdly you haven't indicated what happens if in
parallel clients ask to be served more files than you could
mmap fit into the HTTP server processes address space (ie. see
#2)
So I think this patch stinks :)
next prev parent reply other threads:[~2003-01-02 5:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 1:09 Thomas Ogrisegg
2002-12-30 1:29 ` Larry McVoy
2003-01-02 6:37 ` David S. Miller [this message]
2003-01-02 22:12 ` Thomas Ogrisegg
2003-01-02 22:28 ` Larry McVoy
2003-01-02 23:20 ` Alan Cox
2003-01-02 23:16 ` David S. Miller
2003-01-03 0:56 ` Alan Cox
2003-01-03 2:40 ` David S. Miller
2003-01-03 2:41 ` Linus Torvalds
2003-01-02 23:13 ` David S. Miller
2003-01-03 0:45 ` Thomas Ogrisegg
2003-01-03 1:01 ` Larry McVoy
2003-01-03 1:59 ` Alan Cox
2003-01-06 14:36 ` Gianni Tedesco
2003-01-06 23:29 ` David S. Miller
2003-01-03 1:56 ` Alan Cox
2003-01-03 1:27 ` Larry McVoy
2003-01-03 2:42 ` David S. Miller
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=1041489421.3703.6.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=tom@rhadamanthys.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
Powered by JetHome