На 20.8.2010 г. 11:31, Plamen Petrov написа:
...

The next thing I will be trying is disabling
GRO for the tg3 network card in my network
startup scripts via my shiny new ethtool... ;)

So, for nearly half an hour now running 2.6.36-rc1-FS-00127-g763008c:

root@fs:~# w; uname -a

 12:09:48 up 26 min,  1 user,  load average: 2.43, 1.93, 1.26
USER     TTY      FROM              LOGIN@   IDLE   JCPU   PCPU WHAT
root     pts/0    192.168.10.159   12:09    0.00s  0.02s  0.00s w
Linux fs 2.6.36-rc1-FS-00127-g763008c #1 SMP Thu Aug 19 07:10:57 UTC 2010 i686 Intel(R) Pentium(R) D CPU 3.00GHz GenuineIntel GNU/Linux

And that's with the usual load, which can be found here:
http://pvp.now.im/s/drraw.cgi?Mode=view;Dashboard=1173713287.13177

The only addition I made was running
	ethtool -K ethX gro off
for each network card.

Which means that I have a Broadcom Tygon 3 (tg3) which doesn't
like "generic-receive-offload" at all!

With "generic-receive-offload" off, I will stay on
2.6.36-rc1-FS-00127-g763008c for as long as I can, just to
confirm that in fact the "default on" setting for gro in the
tg3 driver is the culprit for my troubles...

Where to next?