All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralph Doncaster <ralph@istop.com>
To: Jordi Ros <jros@xiran.com>
Cc: "netdev@oss.sgi.com" <netdev@oss.sgi.com>
Subject: RE: TCP IP Offloading Interface
Date: Tue, 15 Jul 2003 15:01:11 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.51.0307151451160.4590@ns.istop.com> (raw)
In-Reply-To: <E3738FB497C72449B0A81AEABE6E713C027A43@STXCHG1.simpletech.com>

On Mon, 14 Jul 2003, Jordi Ros wrote:

> Note that Microsoft is considering TOE under its Scalable Networking Program. To keep linux competitive, I would encourage a healthy discussion on this matter. Again, TOE is not the goal but the means to deliver important technologies for the next generation of servers. This will be critical as the backbone of the Internet goes to all optical networks while the servers stay at the electronic domain. As shown by McKeown, "Circuit Switching in the Core", the line capacity of the optical fibers is doubling every 7 months while the processing CPU capacity (Moore's law) can only double every 18 months.

Moore's law is borne out in practice; most optical tansmission
developments are theory.  3 years ago the fastest circuit you could
readily buy from a carrier (QWest, 360, Williams, etc) was OC192.  Today I
still can't contact a rep from any of those companies and order an OC768.

Even so, as things currently stand in Linux, an application can send a
stream of data from a file on disk to the network without any of the data
touching the CPU.  So we really don't need any new and convoluted way of
accelerating network performance.

> PROPRIETARY-CONFIDENTIAL INFORMATION INCLUDED

And you expect to be taken seriously when you include a stupid disclaimer
like this at the end of your email?

-Ralph

  parent reply	other threads:[~2003-07-15 19:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15  5:42 TCP IP Offloading Interface 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 [this message]
2003-07-15 19:36   ` Chris Dukes
  -- strict thread matches above, loose matches on Subject: below --
2003-07-15 16:28 David griego
2003-07-13  7:33 Alan Shih
2003-07-13  7:48 ` 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
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-13 14:51 ` Jeff Garzik

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=Pine.LNX.4.51.0307151451160.4590@ns.istop.com \
    --to=ralph@istop.com \
    --cc=jros@xiran.com \
    --cc=netdev@oss.sgi.com \
    --cc=ralph+d@istop.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.