Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265563AbTFMWZW (ORCPT ); Fri, 13 Jun 2003 18:25:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265564AbTFMWZW (ORCPT ); Fri, 13 Jun 2003 18:25:22 -0400 Received: from dp.samba.org ([66.70.73.150]:34515 "EHLO lists.samba.org") by vger.kernel.org with ESMTP id S265563AbTFMWZV (ORCPT ); Fri, 13 Jun 2003 18:25:21 -0400 Date: Sat, 14 Jun 2003 08:38:41 +1000 From: Anton Blanchard To: Dave Hansen Cc: Herman Dierks , "Feldman, Scott" , David Gibson , Linux Kernel Mailing List , Nancy J Milliner , Ricardo C Gonzalez , Brian Twichell , netdev@oss.sgi.com Subject: Re: e1000 performance hack for ppc64 (Power4) Message-ID: <20030613223841.GB32097@krispykreme> References: <1055521263.3531.2055.camel@nighthawk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1055521263.3531.2055.camel@nighthawk> User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 956 Lines: 22 > Wouldn't you get most of the benefit from copying that stuff around in > the driver if you allocated the skb->data aligned in the first place? Nice try, but my understanding is that on the transmit path we reserve the maximum sized TCP header, copy the data in then form our TCP header backwards from that point. Since the TCP header size changes with various options, its not an easy task. One thing I thought of doing was to cache the current TCP header size and align the next packet based on it, with an extra cacheline at the start for it to spill into if the TCP header grew. This is only worth it if most packets will have the same sized header. Networking guys: is this a valid assumption? Anton - 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/