From owner-freebsd-stable@FreeBSD.ORG Tue Oct 7 19:02:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2CB5106568F; Tue, 7 Oct 2008 19:02:15 +0000 (UTC) (envelope-from joe@osoft.us) Received: from mail.osoft.us (osoft.us [67.14.192.59]) by mx1.freebsd.org (Postfix) with ESMTP id BAC558FC24; Tue, 7 Oct 2008 19:02:15 +0000 (UTC) (envelope-from joe@osoft.us) Received: from [10.0.2.105] (adsl-65-67-81-98.dsl.ltrkar.swbell.net [65.67.81.98]) by mail.osoft.us (Postfix) with ESMTP id 6895333C3D; Tue, 7 Oct 2008 13:33:18 -0500 (CDT) Message-ID: <48EBAB50.5000707@osoft.us> Date: Tue, 07 Oct 2008 13:32:48 -0500 From: Joe Koberg User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Pete French References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: antik@bsd.ee, koitsu@FreeBSD.org, freebsd-stable@freebsd.org Subject: Re: fxp performance with POLLING X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Oct 2008 19:02:16 -0000 Pete French wrote: >> 1 megabit = 106 = 1,000,000 bits which is equal to 125,000 bytes. >> > > you are assuming eight bits per byte - but this is a serial line so > you should use ten bits per byte instead. > > -pete. > That was a rule of thumb in the heyday of async serial lines, which used a start and stop bit per byte. However, ethernet at 100Mbit is 4B5B coded at a 125mhz rate. So the raw synchronous data rate really is 12.5Mbytes/s. Minus the sync preamble of 8 bytes per packet and the mandatory inter-frame-gap of 12 bytes that's a physical layer rate of (12.5M * (1500/(1500+20))) or 12.34Mbyte/s. Even in the later days of modems this rule applied less and less, because the modulation schemes became synchronous. Joe Koberg joe_at_osoft_dot_us