Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 17 Sep 2002 17:43:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 17 Sep 2002 17:43:55 -0400 Received: from pizda.ninka.net ([216.101.162.242]:46979 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Tue, 17 Sep 2002 17:43:53 -0400 Date: Tue, 17 Sep 2002 14:39:47 -0700 (PDT) Message-Id: <20020917.143947.07361352.davem@redhat.com> To: akpm@digeo.com Cc: manfred@colorfullife.com, netdev@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: Info: NAPI performance at "low" loads From: "David S. Miller" In-Reply-To: <3D87A264.8D5F3AD2@digeo.com> References: <3D879F59.6BDF9443@digeo.com> <20020917.142635.114214508.davem@redhat.com> <3D87A264.8D5F3AD2@digeo.com> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1086 Lines: 27 From: Andrew Morton Date: Tue, 17 Sep 2002 14:45:08 -0700 "David S. Miller" wrote: > Well, it is due to the same problems manfred saw initially, > namely just a crappy or buggy NAPI driver implementation. :-) It was due to additional inl()'s and outl()'s in the driver fastpath. How many? Did the implementation cache the register value in a software state word or did it read the register each time to write the IRQ masking bits back? It is issues like this that make me say "crappy or buggy NAPI implementation" Any driver should be able to get the NAPI overhead to max out at 2 PIOs per packet. And if the performance is really concerning, perhaps add an option to use MEM space in the 3c59x driver too, IO instructions are constant cost regardless of how fast the PCI bus being used is :-) - 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/