From: "David S. Miller" <davem@redhat.com>
To: tom@rhadamanthys.org
Cc: linux-kernel@vger.kernel.org, lm@bitmover.com
Subject: Re: [PATCH] TCP Zero Copy for mmapped files
Date: Thu, 02 Jan 2003 18:42:14 -0800 (PST) [thread overview]
Message-ID: <20030102.184214.32718859.davem@redhat.com> (raw)
In-Reply-To: <20030103004543.GA12399@window.dhis.org>
From: Thomas Ogrisegg <tom@rhadamanthys.org>
Date: Fri, 3 Jan 2003 01:45:43 +0100
> This isn't a priority for us. People who want the best possible
> performance can code their apps up to take advantage of sendfile()
> on systems that have it.
So you want to chain people to your "propritaery solution"?
I don't hide my APIs.
> (and really, show me how many systems
> lack a sendfile mechanism these days).
What kind of systems are you talking about? Operating systems?
Nearly all.
HPUX has it, Solaris has it, Microsoft has something very similar,
FreeBSD has it as does I believe NetBSD. Show me the exceptions.
It might be a bit difficult to convert all applications to
sendfile. Especially those for which you don't have the
source code.
If the performance really must be top notch, someone will invest
the time for a given application. Otherwise, if it's not that
important enough to port why should it be important enough to put
a hack into the OS for it?
I don't see your point. Applications which really need the
performance will switch to sendfile anyway because of the
problems with mmap, you mentioned.
Right, so why bother with your patch?
My patch is very simple and takes less than 1KB of code but
will speed up many applications and doesn't have a real
drawback (except when sending "normal" data which is larger
than a page - but that shouldn't happen very often).
What about the extra checks you are placing in a fast path?
prev parent reply other threads:[~2003-01-03 2:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 1:09 [PATCH] TCP Zero Copy for mmapped files Thomas Ogrisegg
2002-12-30 1:29 ` Larry McVoy
2003-01-02 6:37 ` David S. Miller
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 [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=20030102.184214.32718859.davem@redhat.com \
--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