Re: 2.6.12 Performance problems
From: Danial Thom <hidden>
Date: 2005-08-26 03:29:40
Also in:
lkml
Possibly related (same subject, not in this thread)
- 2005-08-21 · Re: 2.6.12 Performance problems · Andrew Morton <hidden>
--- Ben Greear <greearb@candelatech.com> wrote:
Danial Thom wrote:quoted
--- Ben Greear <greearb@candelatech.com>wrote:quoted
quoted
Danial Thom wrote:quoted
I think the concensus is that 2.6 has madetradequoted
offs that lower raw throughput, which iswhatquoted
quoted
aquoted
networking device needs. So as a router or network appliance, 2.6 seems less suitable.Aquoted
quoted
rawquoted
bridging test on a 2.0Ghz operton system: FreeBSD 4.9: Drops no packets at 900K pps Linux 2.4.24: Starts dropping packets at350Kquoted
quoted
ppsquoted
Linux 2.6.12: Starts dropping packets at100Kquoted
quoted
pps I ran some quick tests using kernel 2.6.11,1msquoted
quoted
tick (HZ=1000), SMP kernel. Hardware is P-IV 3.0Ghz + HT on a new SuperMicro motherboard with 64/133Mhz PCI-X bus. NIC is dual Intel pro/1000.Kernelquoted
quoted
is close to stock 2.6.11.quoted
What GigE adapters did you use? Clearly every driver is going to be different. Myexperience isquoted
that a 3.4Ghz P4 is about the performance ofaquoted
2.0Ghz Opteron. I have to try your tuningscriptquoted
tomorrow.Intel pro/1000, as I mentioned. I haven't tried any other NIC that comes close in performance to the e1000.quoted
If your test is still set up, try compiling something large while doing the test. Thedropsquoted
go through the roof in my tests.Installing RH9 on the box now to try some tests... Disk access always robs networking, in my experience, so I am not supprised you see bad ntwk performance while compiling. Ben
It would be useful if there were some way to find out "what" is getting "robbed". If networking has priority, then what is keeping it from getting back to processing the rx interrupts? Ah, the e1000 has built-in interrupt moderation. I can't get into my lab until tomorrow afternoon, but if you get a chance try setting ITR in e1000_main.c to something larger, like 20K. and see if it makes a difference. At 200K pps that would cause an interrupt every 10 packets, which may allow the routine to grab back the cpu more often. Danial __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com