From: "David S. Miller" <davem@redhat.com>
To: jgarzik@mandrakesoft.com
Cc: chen_xiangping@emc.com, linux-kernel@vger.kernel.org
Subject: Re: Tcp/ip offload card driver
Date: Fri, 10 May 2002 08:07:25 -0700 (PDT) [thread overview]
Message-ID: <20020510.080725.94585622.davem@redhat.com> (raw)
In-Reply-To: <3CDBE34A.8050806@mandrakesoft.com>
From: Jeff Garzik <jgarzik@mandrakesoft.com>
Date: Fri, 10 May 2002 11:12:10 -0400
Linux TCP implementation will always be more powerful and more flexible
than any NIC, too. I doubt they have netlink and netfilter on NICs, for
example :)
It has the same problem as proprietary implementations of the BSD
stack, same bugs and same enhancements done N-times instead of once.
Anyone who thinks that having a different TCP implementation on each
different kind of network card installed on your system is sane, would
you please pass it on brotha so I can smoke some of it too! :-)
On a more serious note, it might be at some level considerable (the
maintainence nightmare et al.) if there was some real life
demonstrable performance gain with current systems.
For example, do a SpecWEB run with TUX both using on-chip-TCP and
without, same networking card. Show a demonstrable gain from the
on-chip-TCP implementation. I bet you can't. If you can make such a
claim using a setup that other people could reproduce themselves by
buying your card and running the test, I'll eat all of my words.
next prev parent reply other threads:[~2002-05-10 15:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 14:48 Tcp/ip offload card driver chen, xiangping
2002-05-10 14:43 ` David S. Miller
2002-05-10 15:11 ` Pedro M. Rodrigues
2002-05-10 15:04 ` David S. Miller
2002-05-10 16:59 ` Jesse Pollard
2002-05-11 22:23 ` Oliver Xymoron
2002-05-10 15:31 ` Jeff Garzik
2002-05-10 15:51 ` Nicholas Harring
2002-05-10 15:49 ` David S. Miller
2002-05-10 16:04 ` Nicholas Harring
2002-05-10 16:09 ` Joel Jaeggli
2002-05-12 0:55 ` john slee
2002-05-12 17:36 ` Mr. James W. Laferriere
2002-05-10 18:36 ` Eric W. Biederman
2002-05-10 16:02 ` Mark Hahn
2002-05-10 15:12 ` Jeff Garzik
2002-05-10 15:07 ` David S. Miller [this message]
2002-05-11 1:53 ` Lincoln Dale
2002-05-12 2:56 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 17:36 Nivedita Singhvi
[not found] <mailman.1021046154.26338.linux-kernel2news@redhat.com>
2002-05-10 17:55 ` Pete Zaitcev
2002-05-10 17:46 ` David S. Miller
2002-05-10 18:39 Nivedita Singhvi
2002-05-10 21:43 Woodruff, Robert J
[not found] <mailman.1021067221.3300.linux-kernel2news@redhat.com>
2002-05-12 2:46 ` Pete Zaitcev
[not found] <Pine.LNX.4.44.0205121335050.14675-100000@filesrv1.baby-dra gons.com>
2002-05-12 22:26 ` Lincoln Dale
2002-05-13 16:17 Woodruff, Robert J
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=20020510.080725.94585622.davem@redhat.com \
--to=davem@redhat.com \
--cc=chen_xiangping@emc.com \
--cc=jgarzik@mandrakesoft.com \
--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 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.