lkml.org 
[lkml]   [2009]   [May]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH 2.6.30-rc4] r8169: avoid losing MSI interrupts
    From
    Date
    On Sat, 2009-05-23 at 18:53 +0200, Michael Riepe wrote:
    >
    > David Dillow wrote:
    > > On Sat, 2009-05-23 at 18:12 +0200, Michael Riepe wrote:
    > >
    > >>If I use two connections (iperf -P2) and nail iperf to both threads of a
    > >>single core with taskset (the program is multi-threaded, just in case
    > >>you wonder), I get this:
    > >>
    > >>CPU 0+2: 0.0-60.0 sec 4.65 GBytes 665 Mbits/sec
    > >>CPU 1+3: 0.0-60.0 sec 6.43 GBytes 920 Mbits/sec
    > >>
    > >>That's quite a difference, isn't it?
    > >>
    > >>Now I wonder what CPU 0 is doing...
    > >
    > >
    > > Where does /proc/interrupts say the irqs are going?
    >
    > Oh well...

    > 27: 48463995 0 0 0 PCI-MSI-edge eth0

    What does it look like if you move the iperf around the CPUs while using
    pci=nomsi?

    I'm looking to make sure I didn't cause a terrible regression in the
    cost of IRQ handling...



    \
     
     \ /
      Last update: 2009-05-23 19:07    [W:0.025 / U:152.148 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site