All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
	linux-kernel@vger.kernel.org, ssharma@us.ibm.com
Subject: Re: socket API extensions workgroup at OpenGroup needs HELP
Date: Wed, 20 Feb 2002 16:06:26 -0800	[thread overview]
Message-ID: <20020220160626.U27423@work.bitmover.com> (raw)
In-Reply-To: <200202202257.g1KMv4c04306@devserv.devel.redhat.com> <E16dgPr-000595-00@the-village.bc.nu>
In-Reply-To: <E16dgPr-000595-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Feb 20, 2002 at 11:44:51PM +0000

> The existing socket API supports zero copy. SGI proved this a long time back
> (Im sure Larry McVoy can give dates). 

Vernon was there long before I was and it worked long before I got there,
all I did was hook up the networking plumbing to the file system plumbing
so that you could move data without copying it.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2002-02-21  0:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1014244622.20316.linux-kernel2news@redhat.com>
2002-02-20 22:57 ` socket API extensions workgroup at OpenGroup needs HELP Pete Zaitcev
2002-02-20 23:21   ` Alexander Viro
2002-02-20 23:33     ` Jan Harkes
2002-02-21  0:00       ` Alexander Viro
2002-02-21  0:05         ` Larry McVoy
2002-02-20 23:44   ` Alan Cox
2002-02-21  0:06     ` Larry McVoy [this message]
     [not found] <200202202257.g1KMv4c04306@devserv.devel.redhat.com.suse.lists.linux.kernel>
     [not found] ` <E16dgPr-000595-00@the-village.bc.nu.suse.lists.linux.kernel>
2002-02-21 12:01   ` Andi Kleen
2002-02-20 14:18 Louis Laborde

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=20020220160626.U27423@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ssharma@us.ibm.com \
    --cc=zaitcev@redhat.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 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.