Received: with ECARTIS (v1.0.0; list netdev); Fri, 20 May 2005 15:34:19 -0700 (PDT) Received: from sunset.davemloft.net (dsl027-180-168.sfo1.dsl.speakeasy.net [216.27.180.168]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j4KMYFF3004049 for ; Fri, 20 May 2005 15:34:16 -0700 Received: from localhost ([127.0.0.1] ident=davem) by sunset.davemloft.net with esmtp (Exim 4.50) id 1DZG3a-00024p-NK; Fri, 20 May 2005 15:33:26 -0700 Date: Fri, 20 May 2005 15:33:26 -0700 (PDT) Message-Id: <20050520.153326.08322399.davem@davemloft.net> To: akepner@sgi.com Cc: mchan@broadcom.com, netdev@oss.sgi.com Subject: Re: Perf data with recent tg3 patches From: "David S. Miller" In-Reply-To: References: <1116031159.6214.8.camel@rh4> <20050513.222007.78719997.davem@davemloft.net> X-Mailer: Mew version 3.3 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 1460 X-ecartis-version: Ecartis v1.0.0 Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com X-original-sender: davem@davemloft.net Precedence: bulk X-list: netdev Content-Length: 715 Lines: 19 From: Arthur Kepner Date: Fri, 20 May 2005 14:52:35 -0700 (PDT) > When the default coalescence parameters are used (rx-frames, > rx-frames-irq both set to 5) the maximum number of received > packets per interrupt is ~4.2. Setting rx-frames and > rx-frames-irq to 20 caused the maximum number of received > packets per interrupt to rise to ~19.6. Maximum CPU > utilization went down from ~52% to ~35%. Very nice. Yes, but using such a high value makes latency go into the toilet. :-) I'd much rather see dynamic settings based upon packet rate. It's easy to resurrect the ancient code from the early tg3 days which does this. Thanks for all your testing, it is very informative and useful.