public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jlnance@unity.ncsu.edu
To: linux-kernel@vger.kernel.org
Subject: Re: sendfile support in linux
Date: Tue, 28 Jan 2003 08:16:00 -0500	[thread overview]
Message-ID: <20030128131600.GA2946@ncsu.edu> (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 

I believe that 2 is only necessary for zero-copy sendfile.  The system
call will work regardless of whether the network card does the TCP
checksum or not.

Thanks,

Jim

  parent reply	other threads:[~2003-01-28 13:06 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 [this message]
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=20030128131600.GA2946@ncsu.edu \
    --to=jlnance@unity.ncsu.edu \
    --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