Jeremy M. Guthrie writes:
> How would I check? It should be in the hundreds of thousands.
Good question Stephen,..
Yes it seems like this pretty hefty load. Forwarding rate of 92k kpps
and a drop rate of 10 kpps and dst hash mostly at 50-60 kentries if
I read the stats correctly.
And 2.4 were able handle this but not 2.6.10?
Assuming things are uses and setup identically. 2.6 uses RCU for route hash
locking. Any dst cache overslow messages seen?
A couple of lines of rtstat would be very interesing from this box.
Also check that the CPU shares the RX packet load. CPU0 affinty to eth0
and CPU1 to eth1 seems to be best. It gives cache bouncing at "TX" and
slab jobs but we have accept that for now.
13:37:25 CPU %user %nice %system %iowait %irq %soft %idle
> 13:38:24 all 0.14 0.00 0.12 0.12 2.02 42.89 54.71
> 13:38:24 0 0.03 0.00 0.05 0.22 0.00 16.67 83.03
> 13:38:24 1 0.25 0.00 0.20 0.03 4.02 69.12 26.40
This looks weird to me... we cannot have CPU left? Due to the imbalance?
Haven't used mpstat. %soft is that *all* softirq's or only softirq's deferred
to ksoftird only?