netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Roland Dreier <roland@topspin.com>,
	"David S. Miller" <davem@redhat.com>,
	Alan Shih <alan@storlinksemi.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: TCP IP Offloading Interface
Date: Sun, 13 Jul 2003 12:58:01 -0400	[thread overview]
Message-ID: <3F118F99.1020104@pobox.com> (raw)
In-Reply-To: <1058113895.554.7.camel@dhcp22.swansea.linux.org.uk>

Alan Cox wrote:
> Finally if you are streaming objects by non mapped references (eg
> sendfile or see LM's paper from long ago on splice()) then the problem
> goes away.


As an aside, I really like sendfile's semantics except for

* People occasionally want to add a receivefile(2).  I disagree... 
sendfile(2) interface should be really be considered a universal 
"fdcopy" interface, regardless of what the 'to' and 'from' file 
descriptors are attached to.  File to socket.  Socket to file.  File to 
file.  socket to socket.  All should be supported, even if the fallback 
is a stupid (but small!) in-kernel copy loop.

* Copy-until-EOF semantics are either undefined, or, unclear to me 
personally.

	Jeff




  parent reply	other threads:[~2003-07-13 16:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ODEIIOAOPGGCDIKEOPILCEMBCMAA.alan@storlinksemi.com>
2003-07-13  7:48 ` TCP IP Offloading Interface David S. Miller
2003-07-13 16:22   ` Roland Dreier
2003-07-13 16:31     ` Alan Cox
2003-07-13 16:49       ` Jeff Garzik
2003-07-13 16:58       ` Jeff Garzik [this message]
2003-07-13 23:02     ` David S. Miller
2003-07-13 23:35       ` Larry McVoy
2003-07-13 23:40         ` David S. Miller
2003-07-13 23:54           ` Larry McVoy
2003-07-13 23:53             ` David S. Miller
2003-07-14  0:22               ` Larry McVoy
2003-07-14  0:24                 ` David S. Miller
2003-07-14  0:48                   ` Larry McVoy
2003-07-14  0:46               ` Valdis.Kletnieks
2003-07-14  0:42                 ` David S. Miller
2003-07-16  2:46                   ` Matt Porter
2003-07-14  0:20       ` Roland Dreier
2003-07-14  0:28         ` David S. Miller
2003-07-16  2:37   ` Matt Porter
2003-07-15  5:42 Jordi Ros
2003-07-15  5:51 ` David S. Miller
2003-07-16  5:02   ` jamal
2003-07-16  1:51     ` Roland Dreier
2003-07-15 19:01 ` Ralph Doncaster
2003-07-15 19:36   ` Chris Dukes
  -- strict thread matches above, loose matches on Subject: below --
2003-07-15 16:28 David griego

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=3F118F99.1020104@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alan@storlinksemi.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=roland@topspin.com \
    /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;
as well as URLs for NNTP newsgroup(s).