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 10:11:03 -0400 (EDT) [thread overview]
Message-ID: <992009463.3b20dcf7467ab@eargle.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0106071322160.22593-100000@age.cs.columbia.edu>
In-Reply-To: <Pine.LNX.4.33.0106071322160.22593-100000@age.cs.columbia.edu>
> 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
next prev parent reply other threads:[~2001-06-08 14:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 22:49 Linux 2.4.5-ac9 Alan Cox
2001-06-06 2:03 ` Keith Owens
2001-06-06 4:32 ` David Ford
2001-06-06 4:39 ` Jeff Garzik
2001-06-06 4:55 ` David Ford
2001-06-06 5:25 ` Keith Owens
2001-06-06 6:08 ` SCSI is as SCSI don't Alan Olsen
2001-06-06 5:39 ` Greg KH
2001-06-06 8:04 ` Alan Olsen
2001-06-06 6:20 ` Alan Olsen
2001-06-06 7:49 ` Alan Cox
2001-06-07 0:00 ` Alan Olsen
2001-06-06 9:15 ` Linux 2.4.5-ac9 Thomas Sailer
2001-06-06 21:43 ` Alan Cox
2001-06-06 10:51 ` Christoph Hellwig
2001-06-06 11:41 ` Thomas Sailer
2001-06-06 13:40 ` Christoph Hellwig
2001-06-06 14:49 ` Chris Liebman
2001-06-06 17:20 ` Tom Sightler
2001-06-06 21:54 ` 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 [this message]
2001-06-08 20:34 ` Ion Badulescu
2001-06-09 1:36 ` Tom Sightler
2001-06-06 22:44 ` Linux 2.4.5-ac9 arjan
-- strict thread matches above, loose matches on Subject: below --
2001-06-08 17:45 xircom_cb problems Tom Sightler
2001-06-08 17:58 ` Arjan van de Ven
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=992009463.3b20dcf7467ab@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