From: Gianni Tedesco <gianni@ecsc.co.uk>
To: Stanley Yee <SYee@snapappliance.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sendfile support in linux
Date: 28 Jan 2003 09:32:05 +0000 [thread overview]
Message-ID: <1043746326.6975.93.camel@lemsip> (raw)
In-Reply-To: <057889C7F1E5D61193620002A537E8690B4387@NCBDC>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
On Tue, 2003-01-28 at 01:45, Stanley Yee wrote:
> I'm trying to find out more about sendfile(2). So far, from what I've
> gathered, it sounds like the requirements for it are (please correct me if
> I'm wrong):
>
> 1. A kernel with sendfile support (i.e. 2.4.X)
> 2. A network card capable of doing the TCP checksum in the hardware
> 3. The application must support sendfile
Those are the user requirements yes. Of course the programmer only needs
to assume (1) to start writing applications. Oh and its probably worth
mentioning:
4. You can't do zero-copy receive.
> Do you know what applications support zerocopy (sendfile)? I noticed that a
> zerocopy NFS patch was added to the 2.5.x tree. Does the 2.4.X NFS daemon
> support zerocopy? Does samba support zerocopy and if so what version?
Samba, tux2, apache?, all the big stuff.
Dunno about NFS.
--
// Gianni Tedesco (gianni at scaramanga dot co dot uk)
lynx --source www.scaramanga.co.uk/gianni-at-ecsc.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-28 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 1:45 sendfile support in linux Stanley Yee
2003-01-28 9:32 ` Gianni Tedesco [this message]
2003-01-28 13:16 ` jlnance
2003-01-28 17:22 ` Oliver Xymoron
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=1043746326.6975.93.camel@lemsip \
--to=gianni@ecsc.co.uk \
--cc=SYee@snapappliance.com \
--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.