Re: 2.6.12 Performance problems

From: Danial Thom (danial_thom_at_yahoo.com)
Date: 08/27/05

  • Next message: VIERA FORD: "confidential"
    Date:	Fri, 26 Aug 2005 15:18:52 -0700 (PDT)
    To: Ben Greear <greearb@candelatech.com>
    
    

    --- Danial Thom <danial_thom@yahoo.com> wrote:

    >
    >
    > --- Ben Greear <greearb@candelatech.com> wrote:
    >
    > > Danial Thom wrote:
    > > >
    > > > --- Ben Greear <greearb@candelatech.com>
    > > wrote:
    > > >
    > > >
    > > >>Danial Thom wrote:
    > > >>
    > > >>
    > > >>>I think the concensus is that 2.6 has made
    > > >>
    > > >>trade
    > > >>
    > > >>>offs that lower raw throughput, which is
    > > what
    > > >>
    > > >>a
    > > >>
    > > >>>networking device needs. So as a router or
    > > >>>network appliance, 2.6 seems less
    > suitable.
    > > A
    > > >>
    > > >>raw
    > > >>
    > > >>>bridging test on a 2.0Ghz operton system:
    > > >>>
    > > >>>FreeBSD 4.9: Drops no packets at 900K pps
    > > >>>Linux 2.4.24: Starts dropping packets at
    > > 350K
    > > >>
    > > >>pps
    > > >>
    > > >>>Linux 2.6.12: Starts dropping packets at
    > > 100K
    > > >>
    > > >>pps
    > > >>
    > > >>I ran some quick tests using kernel 2.6.11,
    > > 1ms
    > > >>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.
    > > Kernel
    > > >>is close to stock 2.6.11.
    > >
    > > > What GigE adapters did you use? Clearly
    > every
    > > > driver is going to be different. My
    > > experience is
    > > > that a 3.4Ghz P4 is about the performance
    > of
    > > a
    > > > 2.0Ghz Opteron. I have to try your tuning
    > > script
    > > > tomorrow.
    > >
    > > Intel pro/1000, as I mentioned. I haven't
    > > tried any other
    > > NIC that comes close in performance to the
    > > e1000.
    > >
    > > > If your test is still set up, try compiling
    > > > something large while doing the test. The
    > > drops
    > > > 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
    >

    Just FYI, setting interrupt moderation to 20,000
    didn't make much difference.

                    
    ____________________________________________________
    Start your day with Yahoo! - make it your home page
    http://www.yahoo.com/r/hs
     
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: VIERA FORD: "confidential"

    Relevant Pages

    • Re: [PATCH] 3c59x: read current link status from phy
      ... there is only one interrupt that for data transmission (both Tx ... The MII registers are not ... Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: is killing zombies possible w/o a reboot?
      ... An interrupt could be received at any time, ... in uninterruptible state because it is uninterruptible ... Processes must never get stuck in D, it's a kernel bug. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.0-test7-mm1
      ... >> handlers happens to start a thread, ... Problem is, things like bus resets happen in interrupt, and while I can ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: CONFIG_IRQBALANCE for AMD64?
      ... Provide some sort of cache-affinity for network interrupt processing, ... Utilize idle CPUs where possible to shoulder the load. ... I'll confess to not having looked at non-i386 arches. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.28-1
      ... >with our inhouse java project under a Blackdown 1.4 jdk. ... get to a con, I'm sure it does, because hitting the keys generates an interrupt ... then try hitting Sysrq+T when it hangs. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)