mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stanley Yee <SYee@snapappliance.com>
To: "'Gianni Tedesco'" <gianni@ecsc.co.uk>,
	Stanley Yee <SYee@snapappliance.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: sendfile support in linux
Date: Mon, 27 Jan 2003 17:45:20 -0800	[thread overview]
Message-ID: <057889C7F1E5D61193620002A537E8690B4387@NCBDC> (raw)

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 

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?

Only me,
Stanley Yee

-----Original Message-----
From: Gianni Tedesco [mailto:gianni@ecsc.co.uk]
Sent: Thursday, January 23, 2003 1:14 AM
To: Stanley Yee
Cc: Linux Kernel Mailing List
Subject: Re: Zero copy in 2.4 kernels


On Wed, 2003-01-22 at 01:48, Stanley Yee wrote:
> Is the zero copy function enabled by default in the 2.4.X kernels?  If so
> which kernel version and what do I need to do to enable it?  Thanks for
your
> time.

sendfile(2) does zero-copy writes from files to sockets, works on any
version of 2.4 AFAIK.

HTH

-- 
// 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

             reply	other threads:[~2003-01-28  1:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28  1:45 Stanley Yee [this message]
2003-01-28  9:32 ` Gianni Tedesco
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=057889C7F1E5D61193620002A537E8690B4387@NCBDC \
    --to=syee@snapappliance.com \
    --cc=gianni@ecsc.co.uk \
    --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

all inboxes | Powered by JetHome®