Skip to contentSkip to conversation

ne2k-pci uncorrectly detecting collisions ?

DISCUSSION Lucas Nussbaum 4 participants 6 messages May 5, 2004 – May 6, 2004

lore
Share & tools
lore
#0 lore raw

Hello,

I have experienced problem with the ne2k-pci driver. The symptoms were extremly poor performance with TCP. After some investigations, I believe it might be caused by problems with detecting collisions.

I tested with 3 cards :
- eth1 : RTL8029 - not working properly
the chip says RTL8029, but lspci says RTL8029(AS)
- eth2 : RTL8029AS - working.
- eth3 : RTL8029AS - not working properly
lspci for all three cards :
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)

The same problem was experienced on FreeBSD, but it hurts a lot to say that there wasn't any problem when I tested under Windows - so it's probably not a broken card problem.

All 3 NICs were in the same box, using the same ne2k-pci driver compiled as a module (kernel version is 2.4.24). They used the same 10/100 Hub to talk to the same NIC on the other end. Traffic on the network during the test was quite low but not nonexistent.

As you can see :
- throughput for eth1 and eth3 with TCP is extremly low.
- throughput with UDP is normal.
- eth1 and eth3 saw no collisions, but eth2 saw a lot.
- eth1 and eth3 saw lots of frame errors, but eth2 saw much less.

Here are the detailed test results. I can provide more results if needed.
+ ifconfig eth1 down
+ ifconfig eth2 down
+ ifconfig eth3 down
+ rmmod ne2k-pci
+ modprobe ne2k-pci
+ ifconfig eth1 172.36.1.2
+ ifconfig eth2 172.37.1.2
+ ifconfig eth3 172.38.1.2
+ netperf -H 172.36.1.1 -l 20
TCP STREAM TEST to 172.36.1.1

Recv   Send    Send                          
Socket Socket  Message  Elapsed              
Size   Size    Size     Time     Throughput  
bytes  bytes   bytes    secs.    10^6bits/sec  

87380 16384 16384 20.18 0.59
+ netperf -H 172.37.1.1 -l 20
TCP STREAM TEST to 172.37.1.1

Recv   Send    Send                          
Socket Socket  Message  Elapsed              
Size   Size    Size     Time     Throughput  
bytes  bytes   bytes    secs.    10^6bits/sec  

87380 16384 16384 20.04 8.54
+ netperf -H 172.38.1.1 -l 20
TCP STREAM TEST to 172.38.1.1

Recv   Send    Send                          
Socket Socket  Message  Elapsed              
Size   Size    Size     Time     Throughput  
bytes  bytes   bytes    secs.    10^6bits/sec  

87380 16384 16384 20.05 0.56
+ netperf -t UDP_STREAM -H 172.36.1.1 -l 20 -- -m 1472 UDP UNIDIRECTIONAL SEND TEST to 172.36.1.1

Socket  Message  Elapsed      Messages                
Size    Size     Time         Okay Errors   Throughput
bytes   bytes    secs            #      #   10^6bits/sec
 65535    1472   20.00       16027      0       9.44
 65535           20.00       15216              8.96

+ netperf -t UDP_STREAM -H 172.37.1.1 -l 20 -- -m 1472 UDP UNIDIRECTIONAL SEND TEST to 172.37.1.1

Socket  Message  Elapsed      Messages                
Size    Size     Time         Okay Errors   Throughput
bytes   bytes    secs            #      #   10^6bits/sec
 65535    1472   19.99       15326      0       9.03
 65535           19.99       15326              9.03

+ netperf -t UDP_STREAM -H 172.38.1.1 -l 20 -- -m 1472 UDP UNIDIRECTIONAL SEND TEST to 172.38.1.1

Socket  Message  Elapsed      Messages                
Size    Size     Time         Okay Errors   Throughput
bytes   bytes    secs            #      #   10^6bits/sec
 65535    1472   20.00       16008      0       9.43
 65535           20.00       15593              9.18

+ netstat -i
Table d'interfaces noyau
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg

eth0   1500 0    140926      0      0      0  232637      0      0      0 BMRU
eth1   1500 0      1049      0      0      0   17292      0      0      0 BMRU
eth2   1500 0      7421      0      0      0   30134      0      0      0 BMRU
eth3   1500 0       982      0      0      0   17201      0      0      0 BMRU
lo    16436 0     22831      0      0      0   22831      0      0      0 LRU
+ ifconfig eth1
eth1      Lien encap:Ethernet  HWaddr 00:00:E8:D7:E9:46  
          inet adr:172.36.1.2  Bcast:172.36.255.255  Masque:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1049 errors:0 dropped:0 overruns:0 frame:165
          TX packets:17292 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:75796 (74.0 KiB)  TX bytes:26148738 (24.9 MiB)
          Interruption:5 Adresse de base:0xd800 

+ ifconfig eth2
eth2 Lien encap:Ethernet HWaddr 00:E0:7D:75:C2:D7

          inet adr:172.37.1.2  Bcast:172.37.255.255  Masque:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7421 errors:0 dropped:0 overruns:0 frame:27
          TX packets:30134 errors:0 dropped:0 overruns:0 carrier:0
          collisions:225 lg file transmission:1000 
          RX bytes:491544 (480.0 KiB)  TX bytes:45590838 (43.4 MiB)
          Interruption:9 Adresse de base:0xdc00 

+ ifconfig eth3
eth3 Lien encap:Ethernet HWaddr 00:00:E8:74:0E:1A

          inet adr:172.38.1.2  Bcast:172.38.255.255  Masque:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:982 errors:0 dropped:0 overruns:0 frame:147
          TX packets:17201 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:71062 (69.3 KiB)  TX bytes:26010052 (24.8 MiB)
          Interruption:11 Adresse de base:0xe000 

Thank you,

Signature · 4 lines
| Lucas Nussbaum
| [email protected]    [email protected]    GPG: 1024D/023B3F4F |
| jabber: [email protected]   http://www.lucas-nussbaum.net |
| fingerprint: 075D 010B 80C3 AC68 BD4F B328 DA19 6237 023B 3F4F |
#1 lore raw

I think that problem, it's because hardware, ne2k-pci NIC's and all realtek stuff, are chip NIC's that it's not suposed to use in that way, i have many problems like that, with realtek NIC's, but when i used real NIC's like 3com, you dont have any problems at all! The realtek's NIC's starts complaining because another ones, they dont live well together! :)
Buy 3com nic's. :)

good luck

Quoted 138 lines · On Wed, 5 May 2004 14:35:32 +0200 Lucas Nussbaum <[email protected]>…

Hello,

I have experienced problem with the ne2k-pci driver. The symptoms were extremly poor performance with TCP. After some investigations, I believe it might be caused by problems with detecting collisions.

I tested with 3 cards :
- eth1 : RTL8029 - not working properly
the chip says RTL8029, but lspci says RTL8029(AS)
- eth2 : RTL8029AS - working.
- eth3 : RTL8029AS - not working properly
lspci for all three cards :
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)

The same problem was experienced on FreeBSD, but it hurts a lot to say that there wasn't any problem when I tested under Windows - so it's probably not a broken card problem.

All 3 NICs were in the same box, using the same ne2k-pci driver compiled as a module (kernel version is 2.4.24). They used the same 10/100 Hub to talk to the same NIC on the other end. Traffic on the network during the test was quite low but not nonexistent.

As you can see :
- throughput for eth1 and eth3 with TCP is extremly low.
- throughput with UDP is normal.
- eth1 and eth3 saw no collisions, but eth2 saw a lot.
- eth1 and eth3 saw lots of frame errors, but eth2 saw much less.

Here are the detailed test results. I can provide more results if needed.
+ ifconfig eth1 down
+ ifconfig eth2 down
+ ifconfig eth3 down
+ rmmod ne2k-pci
+ modprobe ne2k-pci
+ ifconfig eth1 172.36.1.2
+ ifconfig eth2 172.37.1.2
+ ifconfig eth3 172.38.1.2
+ netperf -H 172.36.1.1 -l 20
TCP STREAM TEST to 172.36.1.1

Recv   Send    Send                          
Socket Socket  Message  Elapsed              
Size   Size    Size     Time     Throughput  
bytes  bytes   bytes    secs.    10^6bits/sec  

87380 16384 16384 20.18 0.59
+ netperf -H 172.37.1.1 -l 20
TCP STREAM TEST to 172.37.1.1

Recv   Send    Send                          
Socket Socket  Message  Elapsed              
Size   Size    Size     Time     Throughput  
bytes  bytes   bytes    secs.    10^6bits/sec  

87380 16384 16384 20.04 8.54
+ netperf -H 172.38.1.1 -l 20
TCP STREAM TEST to 172.38.1.1

Recv   Send    Send                          
Socket Socket  Message  Elapsed              
Size   Size    Size     Time     Throughput  
bytes  bytes   bytes    secs.    10^6bits/sec  

87380 16384 16384 20.05 0.56
+ netperf -t UDP_STREAM -H 172.36.1.1 -l 20 -- -m 1472 UDP UNIDIRECTIONAL SEND TEST to 172.36.1.1

Socket  Message  Elapsed      Messages                
Size    Size     Time         Okay Errors   Throughput
bytes   bytes    secs            #      #   10^6bits/sec
 65535    1472   20.00       16027      0       9.44
 65535           20.00       15216              8.96

+ netperf -t UDP_STREAM -H 172.37.1.1 -l 20 -- -m 1472 UDP UNIDIRECTIONAL SEND TEST to 172.37.1.1

Socket  Message  Elapsed      Messages                
Size    Size     Time         Okay Errors   Throughput
bytes   bytes    secs            #      #   10^6bits/sec
 65535    1472   19.99       15326      0       9.03
 65535           19.99       15326              9.03

+ netperf -t UDP_STREAM -H 172.38.1.1 -l 20 -- -m 1472 UDP UNIDIRECTIONAL SEND TEST to 172.38.1.1

Socket  Message  Elapsed      Messages                
Size    Size     Time         Okay Errors   Throughput
bytes   bytes    secs            #      #   10^6bits/sec
 65535    1472   20.00       16008      0       9.43
 65535           20.00       15593              9.18

+ netstat -i
Table d'interfaces noyau
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg

eth0   1500 0    140926      0      0      0  232637      0      0      0 BMRU
eth1   1500 0      1049      0      0      0   17292      0      0      0 BMRU
eth2   1500 0      7421      0      0      0   30134      0      0      0 BMRU
eth3   1500 0       982      0      0      0   17201      0      0      0 BMRU
lo    16436 0     22831      0      0      0   22831      0      0      0 LRU
+ ifconfig eth1
eth1      Lien encap:Ethernet  HWaddr 00:00:E8:D7:E9:46  
          inet adr:172.36.1.2  Bcast:172.36.255.255  Masque:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1049 errors:0 dropped:0 overruns:0 frame:165
          TX packets:17292 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:75796 (74.0 KiB)  TX bytes:26148738 (24.9 MiB)
          Interruption:5 Adresse de base:0xd800 

+ ifconfig eth2
eth2 Lien encap:Ethernet HWaddr 00:E0:7D:75:C2:D7

          inet adr:172.37.1.2  Bcast:172.37.255.255  Masque:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7421 errors:0 dropped:0 overruns:0 frame:27
          TX packets:30134 errors:0 dropped:0 overruns:0 carrier:0
          collisions:225 lg file transmission:1000 
          RX bytes:491544 (480.0 KiB)  TX bytes:45590838 (43.4 MiB)
          Interruption:9 Adresse de base:0xdc00 

+ ifconfig eth3
eth3 Lien encap:Ethernet HWaddr 00:00:E8:74:0E:1A

          inet adr:172.38.1.2  Bcast:172.38.255.255  Masque:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:982 errors:0 dropped:0 overruns:0 frame:147
          TX packets:17201 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:71062 (69.3 KiB)  TX bytes:26010052 (24.8 MiB)
          Interruption:11 Adresse de base:0xe000 

Thank you,

Signature · 9 lines
| Lucas Nussbaum
| [email protected]    [email protected]    GPG: 1024D/023B3F4F |
| jabber: [email protected]   http://www.lucas-nussbaum.net |
| fingerprint: 075D 010B 80C3 AC68 BD4F B328 DA19 6237 023B 3F4F |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
#2 lore raw
In reply to Lucas Nussbaum
Quoted 6 lines · Lucas Nussbaum

Hello,

I have experienced problem with the ne2k-pci driver. The symptoms were extremly poor performance with TCP. After some investigations, I believe it might be caused by problems with detecting collisions.

But software doesn't detect collisions. It just records what hardware said it did. It looks like you have a 10 Mb/s card on a 100 Mb/s network. The collisions reported are how the hardware throttles the difference in physical-link speed.

It is possible that software didn't initialize a 100 Mb/s device and instead initialized it to 10 Mb/s, but you don't have any evidence of that presented.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5557.45 BogoMips).
Note 96.31% of all statistics are fiction.

#3 lore raw
Quoted 9 lines · Richard B. Johnson
Quoted 4 lines

I have experienced problem with the ne2k-pci driver. The symptoms were extremly poor performance with TCP. After some investigations, I believe it might be caused by problems with detecting collisions.

But software doesn't detect collisions. It just records what hardware said it did. It looks like you have a 10 Mb/s card on a 100 Mb/s network. The collisions reported are how the hardware throttles the difference in physical-link speed.

The hub is a 10/100 one, and the 3 RTL8029 are 10 Mbps only.

Quoted 3 lines

It is possible that software didn't initialize a 100 Mb/s device and instead initialized it to 10 Mb/s, but you don't have any evidence of that presented.

No, because RTL8029 are 10 mbps only (they are BNC/RJ45 NICs).

But what I thought was that maybe, they were initialised as full duplex, not half duplex. But again, I don't know where I can check that. I added some printks and determined that the code used to init them full duplex was never used. And there's no way to force them half duplex with this driver.

Lucas

#4 lore raw
Quoted 16 lines · Lucas Nussbaum
Quoted 8 lines · Richard B. Johnson
Quoted 3 lines

I have experienced problem with the ne2k-pci driver. The symptoms were extremly poor performance with TCP. After some investigations, I believe it might be caused by problems with detecting collisions.

But software doesn't detect collisions. It just records what hardware said it did. It looks like you have a 10 Mb/s card on a 100 Mb/s network. The collisions reported are how the hardware throttles the difference in physical-link speed.

The hub is a 10/100 one, and the 3 RTL8029 are 10 Mbps only.

Quoted 3 lines

It is possible that software didn't initialize a 100 Mb/s device and instead initialized it to 10 Mb/s, but you don't have any evidence of that presented.

Quoted 7 lines

No, because RTL8029 are 10 mbps only (they are BNC/RJ45 NICs).

But what I thought was that maybe, they were initialised as full duplex, not half duplex. But again, I don't know where I can check that. I added some printks and determined that the code used to init them full duplex was never used. And there's no way to force them half duplex with this driver.

There is a DOS utility which configure duplex settings for RTL8029.

Also check /proc/interrupts and /proc/ioports for IRQ/ioport collisions. --
vda

#5 lore raw
Quoted 7 lines · Denis Vlasenko
Quoted 5 lines

But what I thought was that maybe, they were initialised as full duplex, not half duplex. But again, I don't know where I can check that. I added some printks and determined that the code used to init them full duplex was never used. And there's no way to force them half duplex with this driver.

There is a DOS utility which configure duplex settings for RTL8029.

Thanks a lot, that did the trick.

Signature · 4 lines
| Lucas Nussbaum
| [email protected]    [email protected]    GPG: 1024D/023B3F4F |
| jabber: [email protected]   http://www.lucas-nussbaum.net |
| fingerprint: 075D 010B 80C3 AC68 BD4F B328 DA19 6237 023B 3F4F |