[lkml]   [2003]   [Jan]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectGigabit/SMP performance problem

Avery Fay writes:
> I'm working with a dual xeon platform with 4 dual e1000 cards on different
> pci-x buses. I'm having trouble getting better performance with the second
> cpu enabled (ht disabled). With a UP kernel (redhat's 2.4.18), I can route
> about 2.9 gigabits/s at around 90% cpu utilization. With a SMP kernel
> (redhat's 2.4.18), I can route about 2.8 gigabits/s with both cpus at
> around 90% utilization. This suggests to me that the network code is
> serialized. I would expect one of two things from my understanding of the
> 2.4.x networking improvements (softirqs allowing execution on more than
> one cpu):

Well you have a gigabit router :-)

How is your routing setup? Packet size?

Also you'll never get increased performance of a single flow with SMP.
Aggregated performance possible at best. I've been fighting with for some
time too.

You have some important data in /proc/net/softnet_stat which are per cpu
packets received and "cpu collisions" should interest you.

As far as I understand there no serialization in forwarding path except where
it has to be -- when we add softirq's from different cpu into a single device.
This seen in "cpu collisions"

Also here we get into inherent SMP cache bouncing problem with TX interrupts
When TX has skb's which are processed/created in different CPU's. Which CPU
gonna take the interrupt? No matter how we do we run kfree we gona see a lot
of cache bouncing. For systems that have same in/out interface smp_affinity
can be used. In practice this impossible for forwarding.

And this bouncing hurts especially for small pakets....

A litte TX test illustrates. Sender on cpu0.

UP 186 kpps
SMP Aff to cpu0 160 kpps
SMP Aff to cpu0, cpu1 124 kpps
SMP Aff to cpu1 106 kpps

We are playing some code that might decrease this problem.

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

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