From: Larry McVoy <lm@bitmover.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: "Mr. BOFH" <icerbofh@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: Fire Engine??
Date: Tue, 25 Nov 2003 18:11:11 -0800 [thread overview]
Message-ID: <20031126021111.GA10193@work.bitmover.com> (raw)
In-Reply-To: <3FC40663.6050602@cyberone.com.au>
On Wed, Nov 26, 2003 at 12:48:19PM +1100, Nick Piggin wrote:
>
>
> Mr. BOFH wrote:
>
> >Sun has announced that they have redone their TCP/IP stack and is showing
> >for some instances a 30% improvement over Linux....
> >
> >http://www.theregister.co.uk/content/61/33440.html
> >
> >
>
> Thats odd. Since when did Linux's TCP/IP stack become the benchmark? :)
>
> PS. This isn't really appropriate for this list. I'm sure an open and
> verifiable comparison would be welcomed though.
And not to dis my Alma Mater but I tend think the whole TOE idea is a lose.
I used to think otherwise, while I was a Sun employee, and Sun employee #1
pointed out to me that CPUs and memory were getting faster more quickly than
the TOE type answers could come to market. He was right then and he seems
to still be right.
Maybe throwing processors at the problem will make him (and me now) wrong
but I have to think I could do better things with a CPU than offload some
TCP packets.
Linux has it right. Make the normal case fast and lightweight and ignore
the other cases. There are no other cases if the normal path is fast.
Another way to say "fast path" is "our normal path sucks".
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-11-26 2:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 0:15 Fire Engine?? Mr. BOFH
2003-11-26 1:48 ` [OT] " Nick Piggin
2003-11-26 2:11 ` Larry McVoy [this message]
2003-11-26 2:48 ` David S. Miller
2003-11-26 3:31 ` Rik van Riel
2003-11-26 2:30 ` David S. Miller
2003-11-26 5:41 ` Valdis.Kletnieks
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=20031126021111.GA10193@work.bitmover.com \
--to=lm@bitmover.com \
--cc=icerbofh@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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).