From: Tom Sightler <ttsig@tuxyturvy.com>
To: Ion Badulescu <ionut@cs.columbia.edu>
Cc: Tom Sightler <ttsig@tuxyturvy.com>,
linux-kernel@vger.kernel.org, arjan@fenrus.demon.nl
Subject: Re: xircom_cb problems
Date: Fri, 08 Jun 2001 13:45:02 -0400 (EDT) [thread overview]
Message-ID: <992022302.3b210f1e0e26f@eargle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
Whoops!! Sorry, forgot the attachment.
Thanks,
Tom
> Both of these are slow, actually. I'm getting 7.5-8MB/s when receiving
> from a 100Mbit box (tulip or starfire, doesn't seem to matter).
> Transmitting is still slow for me, but that is most likely a different
> problem -- and I'm looking into it.
Yeah, I knew they were both slow, but at least one is acceptable, the <200KB/s
is below usable when doing any network based work.
> Moreover, I'm getting 9+MB/s in both directions when using the other
> driver (xircom_tulip_cb), patched to do half-duplex only. So the card
> can definitely transfer at network speeds.
I'm not doing nearly as well with the other driver, but I don't have it patched
for half-duplex only. I tried setting the remote end to force half-duplex but
this didn't seem to work quite right.
> Looking forward to seeing them...
OK, I tried your patch, it did fix the problem where pump wouldn't pull an IP
address, but I'm still having the problem where my ping times go nuts. I've
attached an example, it's 100% repeatable on my network at work. It was so bad
I couldn't get any benchmark numbers.
Later,
Tom
[-- Attachment #2: /root/xircom-slow-pings.txt --]
[-- Type: text/plain, Size: 1975 bytes --]
[root@iso-2146-l1 ttsig]# ping 10.10.4.254
PING 10.10.4.254 (10.10.4.254) from 10.10.4.33 : 56(84) bytes of data.
64 bytes from 10.10.4.254: icmp_seq=3 ttl=255 time=590 usec
64 bytes from 10.10.4.254: icmp_seq=0 ttl=255 time=2.996 sec
64 bytes from 10.10.4.254: icmp_seq=1 ttl=255 time=2.000 sec
64 bytes from 10.10.4.254: icmp_seq=2 ttl=255 time=1.000 sec
64 bytes from 10.10.4.254: icmp_seq=7 ttl=255 time=575 usec
64 bytes from 10.10.4.254: icmp_seq=4 ttl=255 time=3.000 sec
64 bytes from 10.10.4.254: icmp_seq=5 ttl=255 time=2.000 sec
64 bytes from 10.10.4.254: icmp_seq=6 ttl=255 time=1.000 sec
--- 10.10.4.254 ping statistics ---
10 packets transmitted, 8 packets received, 20% packet loss
round-trip min/avg/max/mdev = 0.575/1500.228/3000.710/1117.327 ms
[root@iso-2146-l1 ttsig]# rmmod xircom_cb
rmmod: module xircom_cb is not loaded
[root@iso-2146-l1 ttsig]# lsmod
Module Size Used by
appletalk 18352 0 (autoclean)
serial 44864 0
vmnet 16448 1
vmmon 18352 0
r128 145392 1
agpgart 13568 3 (autoclean)
usb-uhci 20864 0 (unused)
usbcore 48176 1 [usb-uhci]
[root@iso-2146-l1 ttsig]# ping 10.10.4.254
PING 10.10.4.254 (10.10.4.254) from 10.10.4.33 : 56(84) bytes of data.
64 bytes from 10.10.4.254: icmp_seq=0 ttl=255 time=955 usec
64 bytes from 10.10.4.254: icmp_seq=1 ttl=255 time=492 usec
64 bytes from 10.10.4.254: icmp_seq=2 ttl=255 time=453 usec
64 bytes from 10.10.4.254: icmp_seq=3 ttl=255 time=465 usec
64 bytes from 10.10.4.254: icmp_seq=4 ttl=255 time=451 usec
64 bytes from 10.10.4.254: icmp_seq=5 ttl=255 time=455 usec
64 bytes from 10.10.4.254: icmp_seq=6 ttl=255 time=450 usec
64 bytes from 10.10.4.254: icmp_seq=7 ttl=255 time=453 usec
--- 10.10.4.254 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.450/0.521/0.955/0.166 ms
next reply other threads:[~2001-06-08 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-08 17:45 Tom Sightler [this message]
2001-06-08 17:58 ` xircom_cb problems Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2001-06-06 21:54 Linux 2.4.5-ac9 Ion Badulescu
2001-06-07 3:30 ` xircom_cb problems Tom Sightler
2001-06-07 8:31 ` Ion Badulescu
2001-06-07 18:40 ` Tom Sightler
2001-06-07 20:29 ` Ion Badulescu
2001-06-08 14:11 ` Tom Sightler
2001-06-08 20:34 ` Ion Badulescu
2001-06-09 1:36 ` Tom Sightler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=992022302.3b210f1e0e26f@eargle.com \
--to=ttsig@tuxyturvy.com \
--cc=arjan@fenrus.demon.nl \
--cc=ionut@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox