[lkml]   [2000]   [Dec]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject8139too driver broken? (2.4-test12) - Was: Re: rtl8139 driver broken? (2.2.16)
: On Fri, 22 Dec 2000 18:34:46 +0000 (GMT), Alan Cox wrote:

>2.2.18 might help and also as an '8139too' driver rewrite which may work

Advancing further to a 2.4-test12 kernel (with the latest available
8139too driver - 0.9.12) improves the situation even further, but doesn't
solve it.

I still cannot "ping -s 5000" from the 8139too machine, but
at least I can now FTP the 2.4-test12 kernel (18 MB) from another machine
to the 8139 target without any stalls. The rather major problem that
remains is performance.

As before:
* = 8139too (2.4-test12, SuSE 7.0);
HP Omnibook 800; P133; 48 MB

* = eepro100 (2.2.16, SuSE 7.0);
Sony VAIO Z600NE, PIII 650, 256 MB

FTP from (eepro100) to (8139too):

put linux-2.4.0-test12.tar.bz2
18975167 bytes sent in 00:48 (385.71 KB/s)

get linux-2.4.0-test12.tar.bz2
18975167 bytes received in 00:05 (3.18 MB/s)

FTP from (8139too) to (eepro100):

get linux-2.4.0-test12.tar.bz2
18975167 bytes sent in 00:34 (530.39 KB/s)

put linux-2.4.0-test12.tar.bz2
18975167 bytes sent in 00:05 (3.13 MB/s)

IOW, when the 8139too driver itself *delivers* data (put initiated from, get initiated from, I get 3 MB/s throughput,
pretty much what I would expect.

When the 8139too driver gets data pushed down its throat (get initiated
from, put initiated from, then performance
plainly does not exist.

Any ideas?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.060 / U:26.900 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site