linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: "Mr. BOFH" <icerbofh@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fire Engine??
Date: Tue, 25 Nov 2003 18:30:35 -0800	[thread overview]
Message-ID: <20031125183035.1c17185a.davem@redhat.com> (raw)
In-Reply-To: <BAY1-DAV15JU71pROHD000040e2@hotmail.com>

On Tue, 25 Nov 2003 16:15:12 -0800
"Mr. BOFH" <icerbofh@hotmail.com> wrote:

> http://www.theregister.co.uk/content/61/33440.html

This was amusing to read, let's read the claim carefuly,
shall we?

	"We worked hard on efficiency, and we now measure,
	 at a given network workload on identical x86 hardware,
	 we use 30 percent less CPU than Linux."

So his claim is that, in their mesaurements, "CPU utilization"
was lower in their stack.  Was he using 2.6.x and TSO capable
cards on the Linux side?  If not, it's not apples to apples
against are current upcoming technology.

And while his CPU utilization claim is interesting (I bet that gain
would go to zero if they'd used Linux TSO in 2.6.x), but was the
networking bandwidth and latency any better as a result?  I think it's
not by accident that the claim was phrased the way it was.

In fact, I bet their connection setup/teardown latency will go in the
toilet with this stuff and Solaris was already horrible in this area.
It is a well established fact that TOE technologies have this problem
because of how the socket setup/teardown operation with TOE cards
requires the OS to go over the bus a few times.

I'm not worried at all about Sun's fire engine.  It's preliminary
technology, and they are going to discover all of the problem TOE
stuff has that I've discussed several times on this list.

They even mention that they don't even support any current generation
shipping TOE cards yet, at least I offer a cpu utilization reduction
optimization (TSO in 2.6.x) with multiple implementation on current
generation hardware (e1000, tg3, etc.).

I fully welcome them to put Linux up against their incredible fire
engine crap in a sanctioned specweb run on identical hardware.  :)

  parent reply	other threads:[~2003-11-26  2:30 UTC|newest]

Thread overview: 39+ 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
2003-11-26  2:48     ` David S. Miller
2003-11-26  3:31     ` Rik van Riel
2003-11-26  2:30 ` David S. Miller [this message]
2003-11-26  5:41 ` Valdis.Kletnieks
     [not found] <BAY1-DAV15JU71pROHD000040e2@hotmail.com.suse.lists.linux.kernel>
     [not found] ` <20031125183035.1c17185a.davem@redhat.com.suse.lists.linux.kernel>
2003-11-26  9:53   ` Andi Kleen
2003-11-26 11:35     ` John Bradford
2003-11-26 18:50       ` Mike Fedyk
2003-11-26 19:19         ` Diego Calleja García
2003-11-26 19:59           ` Mike Fedyk
2003-11-27  3:54           ` Bill Huey
2003-11-26 15:00     ` Trond Myklebust
2003-11-26 23:01       ` Andi Kleen
2003-11-26 23:23         ` Trond Myklebust
2003-11-26 23:38           ` Andi Kleen
2003-11-26 19:30     ` David S. Miller
2003-11-26 19:58       ` Paul Menage
2003-11-26 20:03         ` David S. Miller
2003-11-26 22:29           ` Andi Kleen
2003-11-26 22:36             ` David S. Miller
2003-11-26 22:56               ` Andi Kleen
2003-11-26 23:13                 ` David S. Miller
2003-11-26 23:29                   ` Andi Kleen
2003-11-26 23:41                   ` Ben Greear
2003-11-26 20:01       ` Jamie Lokier
2003-11-26 20:04         ` David S. Miller
2003-11-26 21:54         ` Pekka Pietikainen
2003-11-26 20:22       ` Theodore Ts'o
2003-11-26 21:02         ` David S. Miller
2003-11-26 21:24           ` Jamie Lokier
2003-11-26 21:38             ` David S. Miller
2003-11-26 23:43               ` Jamie Lokier
2003-11-26 21:34       ` Arjan van de Ven
2003-11-26 22:58         ` Andi Kleen
2003-11-27 12:16           ` Ingo Oeser
2003-11-26 22:39       ` Andi Kleen
2003-11-26 22:46         ` David S. Miller

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=20031125183035.1c17185a.davem@redhat.com \
    --to=davem@redhat.com \
    --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).