From owner-freebsd-hardware  Mon Sep 16 12:43:58 1996
Return-Path: owner-hardware
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA02174
          for hardware-outgoing; Mon, 16 Sep 1996 12:43:58 -0700 (PDT)
Received: from alpo.whistle.com (s205m1.whistle.com [207.76.205.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02152;
          Mon, 16 Sep 1996 12:43:51 -0700 (PDT)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id MAA18330; Mon, 16 Sep 1996 12:38:31 -0700 (PDT)
Message-ID: <323DAC5D.ABD322C@whistle.com>
Date: Mon, 16 Sep 1996 12:37:01 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: Jeffrey Barber <jab@rock.anchorage.net>
CC: "'freebsd-hardware@FreeBSD.org'" <freebsd-hardware@FreeBSD.org>,
        "'hackers@FreeBSD.ORG'" <hackers@FreeBSD.org>
Subject: Re: Very Slow Ethernet Link
References: <01BBA3A2.11B93340@jabpc.rtfm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hardware@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Jeffrey Barber wrote:
> 
> Ok, I just installed FreeBSD 2.1 and boy this is slow, Example:

OK for a start your FreeBSD times are approximatly 1/3 the times
of the linux ones.. 0.3mS vs 1mS

secondly, pinging the loopback interface  doesn't test the ethernet
as the packet never goes anywhere NEAR the ethernet.

thirdly, if the ethernet is slow, and you haven't showed that it
is, you need to give your hardware configuration.
maybe FreeBSD is configured for the wrong interrupt..
that tends to make it slow..


lastly, 2.1 is way old.. you should install 2.1.5 becasue 2.1 is
hard to support as everyone has moved on.


> 
> bash$ ping localhost
> 
> PING localhost (127.0.0.1): 56 data bytes
> 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms
> 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms
> 64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms
> 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms
> 
> --- localhost.arctic.net ping statistics ---
> 6 packets transmitted, 6 packets received, 0% packet loss
> round-trip min/avg/max = 0.342/0.349/0.362 ms
> 
> bash$ ifconfig -a
> 
> lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
> ep0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX> mtu 1500
>         inet 19.51.13.1 netmask 0xffffff00 broadcast 19.51.13.255
> lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 16384
>         inet 127.0.0.1 netmask 0xff000000
> sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
> tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
> 
> On my Linux box I get a ping response of:
> 
> PING localhost (127.0.0.1): 56 data bytes
> 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms
> 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms
> 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms
> 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms
> 
> Big difference here. Please shed some light on this for me.
> 
> TIA