From: Christoph Hellwig <hch@infradead.org>
To: Steve Modica <modica@sgi.com>
Cc: netdev@oss.sgi.com
Subject: Re: Zero copy transmit
Date: Tue, 29 Apr 2003 21:17:37 +0100 [thread overview]
Message-ID: <20030429211737.A9926@infradead.org> (raw)
In-Reply-To: <3EAED567.2090006@sgi.com>; from modica@sgi.com on Tue, Apr 29, 2003 at 02:41:27PM -0500
On Tue, Apr 29, 2003 at 02:41:27PM -0500, Steve Modica wrote:
> At issue is really application capture and customer adoption. There are
> tons of apps and lots of engineers that know socket operations and
> write/writev. Asking all ISVs to recode for linux would leave them with
> two separate APIs to deal with. They would have send/sendto or
> write/writev on Solaris, HPUX and whatever else, and linux would have
> sendfile.
Solaris and HPUX have sendfile, the HPUX one has a slightly different
API, the Solaris one is modelled after Linux.
prev parent reply other threads:[~2003-04-29 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 18:44 Zero copy transmit Steve Modica
2003-04-29 19:20 ` Andi Kleen
2003-04-29 19:33 ` Robin Holt
2003-04-29 19:41 ` Andi Kleen
2003-04-29 19:41 ` Steve Modica
2003-04-29 19:59 ` Andi Kleen
2003-04-29 20:09 ` Steve Modica
2003-04-29 20:39 ` Andi Kleen
2003-04-30 1:41 ` Michael Richardson
2003-04-30 15:05 ` Robin Holt
2003-04-30 15:29 ` Andi Kleen
2003-04-29 20:17 ` Christoph Hellwig [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=20030429211737.A9926@infradead.org \
--to=hch@infradead.org \
--cc=modica@sgi.com \
--cc=netdev@oss.sgi.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).