Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 May 1999 08:04:47 -0400 (EDT)
From:      Dan Janowski <danj@3skel.com>
To:        Warner Losh <imp@harmony.village.org>
Cc:        mobile@FreeBSD.ORG
Subject:   Re: slow ep response...
Message-ID:  <Pine.BSF.4.05.9905040803040.20499-100000@fnur.3skel.com>
In-Reply-To: <199905040537.XAA55127@harmony.village.org>

next in thread | previous in thread | raw e-mail | index | archive | help

PAO3, 3c589c on an unloaded ethernet:

% /sbin/ifconfig ep0
ep0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.168.0.21 netmask 0xffffff00 broadcast 192.168.0.255
        inet 192.168.0.101 netmask 0xffffffff broadcast 192.168.0.101
        ether 00:a0:24:5f:ce:46 


% /sbin/ping 192.168.0.8
PING 192.168.0.8 (192.168.0.8): 56 data bytes
64 bytes from 192.168.0.8: icmp_seq=0 ttl=255 time=0.528 ms
64 bytes from 192.168.0.8: icmp_seq=1 ttl=255 time=0.518 ms
64 bytes from 192.168.0.8: icmp_seq=2 ttl=255 time=0.485 ms
64 bytes from 192.168.0.8: icmp_seq=3 ttl=255 time=0.472 ms
64 bytes from 192.168.0.8: icmp_seq=4 ttl=255 time=0.504 ms
64 bytes from 192.168.0.8: icmp_seq=5 ttl=255 time=0.473 ms
64 bytes from 192.168.0.8: icmp_seq=6 ttl=255 time=0.470 ms

Dan


On Mon, 3 May 1999, Warner Losh wrote:

> 
> I was just able to recreate the slow ep response on my machine here
> (granted, it is running my experiental pccard stuff, which is prone to
> crashing), but I was seeing the following on an unloaded ethernet
> connection:
> 
> % ping 10.5
> PING 10.5 (10.0.0.5): 56 data bytes
> 64 bytes from 10.0.0.5: icmp_seq=0 ttl=255 time=931.404 ms
> 64 bytes from 10.0.0.5: icmp_seq=1 ttl=255 time=1924.132 ms
> 64 bytes from 10.0.0.5: icmp_seq=2 ttl=255 time=914.182 ms
> 64 bytes from 10.0.0.5: icmp_seq=3 ttl=255 time=1904.401 ms
> 64 bytes from 10.0.0.5: icmp_seq=4 ttl=255 time=894.465 ms
> 64 bytes from 10.0.0.5: icmp_seq=5 ttl=255 time=1884.667 ms
> 64 bytes from 10.0.0.5: icmp_seq=6 ttl=255 time=874.722 ms
> 
> This would certainly account for the problems you've been seeing.
> 
> I suspect it has something to do with interrupts, but I'm not sure
> what.  I just wanted to let people know that I've seen this here...
> It seems like it is interrupt related...
> 
> Warner
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-mobile" in the body of the message
> 

--
Dan Janowski     danj@3skel.com       Triskelion Systems, Inc.     Bronx, NY



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9905040803040.20499-100000>