Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264075AbTFPSSn (ORCPT ); Mon, 16 Jun 2003 14:18:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264087AbTFPSSn (ORCPT ); Mon, 16 Jun 2003 14:18:43 -0400 Received: from e1.ny.us.ibm.com ([32.97.182.101]:59348 "EHLO e1.ny.us.ibm.com") by vger.kernel.org with ESMTP id S264075AbTFPSSm (ORCPT ); Mon, 16 Jun 2003 14:18:42 -0400 Subject: RE: e1000 performance hack for ppc64 (Power4) From: Dave Hansen To: "Feldman, Scott" Cc: Herman Dierks , "David S. Miller" , ltd@cisco.com, Anton Blanchard , dwg@au1.ibm.com, Linux Kernel Mailing List , Nancy J Milliner , Ricardo C Gonzalez , Brian Twichell , netdev@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Organization: Message-Id: <1055788229.1609.4.camel@nighthawk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 16 Jun 2003 11:30:29 -0700 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1150 Lines: 28 On Mon, 2003-06-16 at 11:21, Feldman, Scott wrote: > Herman wrote: > > Its only the MTU 1500 case with non-TSO that we are > > discussing here so copying a few bytes is really not a big > > deal as the data is already in cache from copying into > > kernel. If it lets the adapter run at speed, thats what > > customers want and what we need. Granted, if the HW could > > deal with this we would not have to, but thats not the case > > today so I want to spend a few CPU cycles to get best > > performance. Again, if this is not done on other platforms, I > > don't understand why you care. > > I care because adding the arch-specific hack creates a maintenance issue > for Scott, would you be pleased if something was implemented out of the driver, in generic net code? Something that all the drivers could use, even if nothing but e1000 used it for now. -- Dave Hansen haveblue@us.ibm.com - 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/