Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262056AbVCAUfC (ORCPT ); Tue, 1 Mar 2005 15:35:02 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262054AbVCAUfB (ORCPT ); Tue, 1 Mar 2005 15:35:01 -0500 Received: from ns1.lanforge.com ([66.165.47.210]:4493 "EHLO www.lanforge.com") by vger.kernel.org with ESMTP id S262056AbVCAUeo (ORCPT ); Tue, 1 Mar 2005 15:34:44 -0500 Message-ID: <4224D1DF.30909@candelatech.com> Date: Tue, 01 Mar 2005 12:34:39 -0800 From: Ben Greear Organization: Candela Technologies User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3) Gecko/20041020 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-os@analogic.com CC: Linux kernel Subject: Re: Network speed Linux-2.6.10 References: <4224CE98.2060204@candelatech.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1017 Lines: 35 linux-os wrote: > On Tue, 1 Mar 2005, Ben Greear wrote: > I supplied the actual settings. > >> What happens if you just don't muck with the NIC and let it >> auto-negotiate >> on it's own? >> > > It goes to half-duplex and runs 9 to 9.5 megabytes/second as stated > above. > > That's why I think 1/2 duplex is __really__ full-duplex. half-duplex will run near line speed in one direction. Try sending in both directions at the same time and you'll get closer to 40% of the link utilization... Also, if you see any collisions you are in half-duplex mode. You could try connecting the NICs back-to-back with a cross-over cable to take your switch out of the loop? Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.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/