From: Nick Piggin <piggin@cyberone.com.au>
To: "Mr. BOFH" <icerbofh@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: [OT] Re: Fire Engine??
Date: Wed, 26 Nov 2003 12:48:19 +1100 [thread overview]
Message-ID: <3FC40663.6050602@cyberone.com.au> (raw)
In-Reply-To: <BAY1-DAV15JU71pROHD000040e2@hotmail.com>
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.
next prev parent reply other threads:[~2003-11-26 2:05 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 ` Nick Piggin [this message]
2003-11-26 2:11 ` [OT] " Larry McVoy
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=3FC40663.6050602@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=icerbofh@hotmail.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 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).