Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S319266AbSIFQIP>; Fri, 6 Sep 2002 12:08:15 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S319267AbSIFQIO>; Fri, 6 Sep 2002 12:08:14 -0400
Received: from e35.co.us.ibm.com ([32.97.110.133]:43246 "EHLO
	e35.co.us.ibm.com") by vger.kernel.org with ESMTP
	id <S319266AbSIFQIO>; Fri, 6 Sep 2002 12:08:14 -0400
Date: Fri, 06 Sep 2002 09:11:05 -0700
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Reply-To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
cc: "David S. Miller" <davem@redhat.com>, hadi@cyberus.ca,
       tcw@tempest.prismnet.com, linux-kernel@vger.kernel.org,
       netdev@oss.sgi.com, niv@us.ibm.com
Subject: Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000
Message-ID: <52305571.1031303463@[10.10.2.3]>
In-Reply-To: <3D78CBF6.10609@us.ibm.com>
References: <3D78CBF6.10609@us.ibm.com>
X-Mailer: Mulberry/2.1.2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1231
Lines: 27

> No, no.  Bad Martin!  Throughput didn't drop, "Specweb compliance" 
> dropped.   Those are two very, very different things.  I've found 
> that the server can produce a lot more throughput, although it 
> doesn't have the characteristics that Specweb considers compliant.  
> Just have Troy enable mod-status and look at the throughput that 
> Apache tells you that it is giving during a run.  _That_ is real
> throughput, not number of compliant connections.

By throughput I meant number of compliant connections, not bandwidth.
It may well be latency that's going out the window, rather than
bandwidth. Yes, I should use more precise terms ...

> _And_ NAPI is for receive only, right?  Also, my compliance drop 
> occurs with the NAPI checkbox disabled.  There is something else 
> in the new driver that causes our problems.

Not sure about that - I was told once that there were transmission
completion interrupts as well? What happens to those? Or am I 
confused again ...

M.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/