netdev
[Top] [All Lists]

Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000

To: "David S. Miller" <davem@xxxxxxxxxx>
Subject: Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000
From: "Martin J. Bligh" <Martin.Bligh@xxxxxxxxxx>
Date: Fri, 06 Sep 2002 11:51:29 -0700
Cc: gh@xxxxxxxxxx, hadi@xxxxxxxxxx, tcw@xxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, niv@xxxxxxxxxx
In-reply-to: <20020906.113611.102227888.davem@xxxxxxxxxx>
References: <20020906.113611.102227888.davem@xxxxxxxxxx>
Reply-to: "Martin J. Bligh" <Martin.Bligh@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
>    The fact that we're doing something different from everyone else
>    and turning up a different set of kernel issues is a good thing, 
>    to my mind. You're right, we could use Tux if we wanted to ... but
>    that doesn't stop Apache being interesting ;-)
> 
> Tux does not obviate Apache from the equation.
> See my other emails.

That's not the point ... we're getting sidetracked here. The
point is: "is this a realistic-ish stick to beat the kernel
with and expect it to behave" ... I feel the answer is yes.

The secondary point is "what are customers doing in the field?"
(not what *should* they be doing ;-)). Moreover, I think the
Apache + Tux combination has been fairly well beaten on already
by other people in the past, though I'm sure it could be done
again.

I see no reason why turning on NAPI should make the Apache setup
we have perform worse ... quite the opposite. Yes, we could use
Tux, yes we'd get better results. But that's not the point ;-)

M.


<Prev in Thread] Current Thread [Next in Thread>