eepro100 performance problems

[Eric S. Johnson]

Make sure that your switch is also forced into FD mode. Ive basicly given up 
all hope for autosensing, and force the mode on just about every device 
on my network.

Also, for many tcp benchmarks you need to be carefull about the machines 
you use to send and receive. Ive found that a P200 can drive 100Mbit
ether at line speed if it isn't doing anything else. Anything slower
and your are limited by CPU. 

Also note that you will want to increase the socket buffers (hence the 
TCP window) for these tests. Otherwise the window will constrain you.
See below. 

Two identical tests. Sender is a P266 with eepro100 driver
("eepro100.c:v1.08 5/3/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html\n") 
compiled into kernel (not module).

Receiver is a sparc ultra 2/300. 

Both are full duplex on a Nortel/Bay 450T switch.


E

--
esj@vixen:/work/benchmarks/netperf 5% ./netperf.linux  -H grads
TCP STREAM TEST to grads
Recv   Send    Send                          
Socket Socket  Message  Elapsed              
Size   Size    Size     Time     Throughput  
bytes  bytes   bytes    secs.    10^6bits/sec  

  8192  65535  65535    10.01      51.58   
esj@vixen:~/work/benchmarks/netperf 6% ./netperf.linux  -H grads -- -S 133000 
-s 65536 -m 32768
TCP STREAM TEST to grads
Recv   Send    Send                          
Socket Socket  Message  Elapsed              
Size   Size    Size     Time     Throughput  
bytes  bytes   bytes    secs.    10^6bits/sec  

133464 131070  32768    10.00      90.05   
esj@vixen:~/work/benchmarks/netperf 7%