linux-kernel - Re: x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <86802c440901300008x7d2c465cne6c21e4c54e78c3b@mail.gmail.com>
Date:	Fri, 30 Jan 2009 00:08:36 -0800
From:	Yinghai Lu <yhlu.kernel@...il.com>
To:	SUJIT V <sujit.linux@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: x86_64 IOAPIC

On Thu, Jan 29, 2009 at 2:05 PM, SUJIT V <sujit.linux@...il.com> wrote:
> Forgot to mention that we are not using the irqbalance utility.
>
> So which part of the kernel io_apic code is doing the irq balancing
> which we see in /proc/interrupt.
>
> Thanks
>
>
> On Thu, Jan 29, 2009 at 2:02 PM, SUJIT V <sujit.linux@...il.com> wrote:
>> Hi,
>>    We have a IBM Qauadcore 8 CPU system running x86_64 linux 2.6.23.
>> We were doing some performance test. (disk & network).
>> The eth0 IRQ is pinned to CPU0.  The aacraid interrupt has not been
>> assigned any smp affinity.
>>
>> On the system we see in (/proc/interrupts) that when the eth0
>> interrupt rate is high, the aacraid interrupt counter for CPU0 does
>> not increase as much compared to aacraid interrupts handled by other
>> CPUs .
>> This shows that IOAPIC is doing some load balancing.
>>
>> I wanted to check the code which is doing this load balancing. I
>> checked the file arch/x86_64/kernel/io_apic.c. I could not find any
>> irq balancing stuff out there.
>> I went through some archived discussions about the x86_64 ioapic irq
>> balancing. Most of the discussions were about using irqbalance
>> utility.
>>
>>
>> Could some one point me to the relevant piece of io_apic code ?

you are using logical flat mode. and target_cpus and smp_affinity are 0xff.
aka irq is broadcast to all cpus.

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/