On Sat, 17 Jun 2000, Christoph Lameter wrote:
> Briding requires that the ethernet boards operate in promiscuous mode.
> The CPU has to inspect all traffic to check if it needs to be forwarded to
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> another interface... Having Ethernet boards not needing much processing
I know it's a big cpu time consumer. And I could switch to 3Com
EtherLink III (ISA) but I don't think it'll help a lot. I'll try in the
morning just with PCI boards (as Alan sugested), but I don't think it'll
help much. the traffic is still there. :) It feels like the processor it's
not cathing up with the traffic (4 any interfaces in use). btw when all
copying stops, everything's working great.
> and a speedy CPU could be very helpful. But then there is the PCI
^^^^^^^
> bandwidth that will be another limiter.
ah... how speedy? I think a 450mhz is quite a runner. and the 100mhz fsb
improves a lot.
-----------
brg0 Link encap:Ethernet HWaddr FE:FD:0C:81:46:44
inet addr:172.27.33.50 Bcast:172.27.33.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18164 errors:0 dropped:0 overruns:0 frame:0
TX packets:20438 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
eth0 Link encap:Ethernet HWaddr 52:54:05:E2:AA:90
<PCI> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:26239 errors:0 dropped:0 overruns:0 frame:0
TX packets:33644 errors:0 dropped:0 overruns:0 carrier:0
collisions:2 txqueuelen:100
Interrupt:11 Base address:0xf000
eth1 Link encap:Ethernet HWaddr 00:C0:DF:EF:53:03
<PCI> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:777350 errors:0 dropped:0 overruns:0 frame:40
TX packets:63687 errors:0 dropped:0 overruns:0 carrier:0
collisions:475 txqueuelen:100
Interrupt:10 Base address:0xf400
eth2 Link encap:Ethernet HWaddr 00:00:21:4A:54:47
<ISA> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:49850 errors:0 dropped:0 overruns:0 frame:0
TX packets:46995 errors:0 dropped:0 overruns:0 carrier:0
collisions:2 txqueuelen:100
Interrupt:9 Base address:0x340
eth3 Link encap:Ethernet HWaddr 08:00:00:00:05:83
<ISA> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:508 errors:0 dropped:0 overruns:0 frame:0
TX packets:5445 errors:0 dropped:0 overruns:0 carrier:0
collisions:1 txqueuelen:100
Interrupt:4 Base address:0x260
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:46 errors:0 dropped:0 overruns:0 frame:0
TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
---------------
here's ifconfig from a fresh boot, but I had _a lot_ of numbers in the
frame section. and collisions to. hmm..those numbers are big just for the
ISA adapters and backbone/eth1. I've talked with some friends and we
agreed that bad cabling is responsible for collisions. but frames? huh..
and yet I have another problem. If I let the old p5/166 do the
"dirty" and the k6-2 for game hosting, I have a pretty loaded backbone
with peaks over 20ms. normal it doesn't go over 0.6-0.7 ... could be the
cable?
hmm.. so I have to upgrade to 100mb/s backbone adapters/utp?
sorry 4 being persistent, but I realy wanna get to the bottom of this.
/dx
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
