Received: with ECARTIS (v1.0.0; list netdev); Sun, 22 Feb 2004 12:16:22 -0800 (PST) Received: from paix.pilosoft.com (dsl-gw-90.pilosoft.com [69.31.90.1]) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i1MKGIKO014339 for ; Sun, 22 Feb 2004 12:16:19 -0800 Received: from localhost (alex@localhost) by paix.pilosoft.com (8.11.6/8.11.6) with ESMTP id i1MJtEN13049 for ; Sun, 22 Feb 2004 14:55:14 -0500 Date: Sun, 22 Feb 2004 14:55:14 -0500 (EST) From: alex@pilosoft.com To: netdev@oss.sgi.com Subject: kilobit=1000bit Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 3494 X-ecartis-version: Ecartis v1.0.0 Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com X-original-sender: alex@pilosoft.com Precedence: bulk X-list: netdev While trying to investigate mysterios packet loss on a link limited by tc to its theoretical capacity, I realized that tc (and some other tools) treat kilobit as 1024 bits per second. This is manifestly incorrect, as it is pretty much standard for equipment specifications to be given as 1000 bit per second=kilobit. Examples: * Ethernet (10BaseT) is driven by 10Mhz (as in 10 million oscillations per second:) clock, resulting in 10 million bits per second capacity. * Ethernet (100BaseT) is driven by 125Mhz clock and uses 4B/5B encoding resulting in 100 million bits per second capacity. * 56k modem is (details are too long) but it results in 56000 bits/second. I can't think of any networking technology that rates the capacity in 1024 bits/second = kilobit. This may be a just a heads-up to those unaware, but, it would be nice to change tc to use correct multipliers (possibly with a switch to revert to old behavior). -alex