linux-kernel - Re: Pin-pointing the root of unusual application latencies

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Jul 2007 13:09:54 -0400
From:	Len Brown <lenb@...nel.org>
To:	John Sigler <linux.kernel@...e.fr>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-rt-users@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Pin-pointing the root of unusual application latencies

On Wednesday 25 July 2007 10:05, John Sigler wrote:

> # cat /proc/interrupts
>             CPU0
>    0:         37    XT-PIC-XT        timer
>    1:          2    XT-PIC-XT        i8042
>    2:          0    XT-PIC-XT        cascade
>    7:          0    XT-PIC-XT        acpi
>   10:        175    XT-PIC-XT        eth2, Dta1xx
>   11:       1129    XT-PIC-XT        eth0
>   12:          4    XT-PIC-XT        eth1
>   14:      21482    XT-PIC-XT        ide0
> NMI:          0
> LOC:     161632
> ERR:          0
> MIS:          0
> 
> IRQ 10 is shared between a NIC and an I/O board.
> 
> For eth2, the kernel said:
> ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC]
>    -> GSI 10 (level, low) -> IRQ 10
> 
> For Dta1xx, the kernel said:
> ACPI: PCI Interrupt 0000:02:0e.0[A] -> Link [LNKC]
>    -> GSI 10 (level, low) -> IRQ 10
> 
> Is it possible to avoid the two boards sharing IRQ 10?

Maybe.  In this configuration, INTA of the two devices
is physically connected to the same wire on the device-side
of the interrupt re-mapper -- so you'd have to change the configuration.
If you have an IOAPIC and can enable it, that will not hurt --
though unless something else changes, these devices are still
tied together on the device-side of the  mapper.
So if you can physically move one of the devices to another slot
that is your best bet.

I'd need a bunch of info from your system to tell you what
you can do ahead of time, including full dmesg, lspci -vv
and acpidump.

-Len
-
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/