public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Xymoron <oxymoron@waste.org>
To: Stanley Yee <SYee@snapappliance.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sendfile support in linux
Date: Tue, 28 Jan 2003 11:22:36 -0600	[thread overview]
Message-ID: <20030128172236.GR3186@waste.org> (raw)
In-Reply-To: <057889C7F1E5D61193620002A537E8690B4387@NCBDC>

On Mon, Jan 27, 2003 at 05:45:20PM -0800, 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 

Don't confuse sendfile with zerocopy. You generally need to use
sendfile to take advantage of zerocopy, but you can still get
advantages from sendfile without having hardware support, mainly in
terms of reducing syscall overhead. And without sendfile, you can
still get performance benefits from zerocopy..
 
> 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?

Sendfile is mostly used by webservers. You can check the Samba
changelogs for when they started using sendfile. And 2.4 NFS doesn't
use zerocopy, AFAIK.

-- 
 "Love the dolphins," she advised him. "Write by W.A.S.T.E.." 

      parent reply	other threads:[~2003-01-28 17:13 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
2003-01-28 13:16 ` jlnance
2003-01-28 17:22 ` Oliver Xymoron [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=20030128172236.GR3186@waste.org \
    --to=oxymoron@waste.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox