netdev
[Top] [All Lists]

Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000

To: Todd Underwood <todd@xxxxxxxxxxxxx>
Subject: Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000
From: Nivedita Singhvi <niv@xxxxxxxxxx>
Date: Thu, 12 Sep 2002 10:18:37 -0700
Cc: "David S. Miller" <davem@xxxxxxxxxx>, "hadi@xxxxxxxxxx" <hadi@xxxxxxxxxx>, "tcw@xxxxxxxxxxxxxxxxxxxx" <tcw@xxxxxxxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "netdev@xxxxxxxxxxx" <netdev@xxxxxxxxxxx>
In-reply-to: <Pine.LNX.4.44.0209120119580.25406-100000@gp>
References: <Pine.LNX.4.44.0209120119580.25406-100000@gp>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) 3.0
Quoting Todd Underwood <todd@xxxxxxxxxxxxx>:

> sorry for the late reply.  catching up on kernel mail.

> the main different, though, is that general purpose kernel
> development still focussed on the improvements in *sending* speed.
> for real high performance networking, the improvements are necessary
> in *receiving* cpu utilization, in our estimation. 
> (see our analysis of interrupt overhead and the effect on receivers
> at gigabit speeds--i hope that this has become common understanding
> by now)

Some of that may be a byproduct of the "all the worlds' a webserver"
mindset - we are primarily focussed on the server side (aka
money side ;)), and there is some amount of automatic thinking that
this means we're going to be sending data and receiving small packets,
mostly acks) in return. There is much less emphasis given to solving
the problems on the other side (active connection scalability for 
instance), or other issues that manifest themselves as 
client side bottlenecks for most applications..

thanks,
Nivedita


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