Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758193AbYA3OCV (ORCPT ); Wed, 30 Jan 2008 09:02:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756312AbYA3OCG (ORCPT ); Wed, 30 Jan 2008 09:02:06 -0500 Received: from trinity.phys.uwm.edu ([129.89.57.159]:57135 "EHLO trinity.phys.uwm.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756301AbYA3OCE (ORCPT ); Wed, 30 Jan 2008 09:02:04 -0500 Date: Wed, 30 Jan 2008 08:01:46 -0600 (CST) From: Bruce Allen X-X-Sender: ballen@trinity.phys.uwm.edu To: netdev@vger.kernel.org, Linux Kernel Mailing List , David Miller cc: Henning Fehrmann , Carsten Aulbert , Bruce Allen Subject: Re: e1000 full-duplex TCP performance well below wire speed In-Reply-To: <20080130.055333.192844925.davem@davemloft.net> Message-ID: References: <20080130.055333.192844925.davem@davemloft.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1021 Lines: 33 Hi David, Thanks for your note. >> (The performance of a full duplex stream should be close to 1Gb/s in >> both directions.) > > This is not a reasonable expectation. > > ACKs take up space on the link in the opposite direction of the > transfer. > > So the link usage in the opposite direction of the transfer is > very far from zero. Indeed, we are not asking to see 1000 Mb/s. We'd be happy to see 900 Mb/s. Netperf is trasmitting a large buffer in MTU-sized packets (min 1500 bytes). Since the acks are only about 60 bytes in size, they should be around 4% of the total traffic. Hence we would not expect to see more than 960 Mb/s. We have run these same tests on older kernels (with Broadcomm NICS) and gotten above 900 Mb/s full duplex. Cheers, Bruce -- 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/