archive mirror
 help / color / mirror / Atom feed
From: Julien Oster <>
To: Len Brown <>
Cc: Julien Oster <>,
	Linux Kernel Mailing List <>
Subject: Re: balance interrupts
Date: Mon, 08 Dec 2003 21:00:52 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1070911748.2408.39.camel@dhcppc4> (Len Brown's message of "08 Dec 2003 14:29:08 -0500")

Len Brown <> writes:

Hello Len,

> Most IO-APIC systems have PCI interrupt lines hard-wired directly to
> IO-APIC interrupt pins.  If an interrupt isn't where you want it to be,
> you need to physically move a card to another slot so that it gets a
> different wire.  A board with decent documentation will tell you what
> slots get which interrupt wires.

Ah, my board has that kind of documentation. Well, then I might do
just this - or see if my board can do that for me. Also, I'd really
want to know if maybe I can split apart the two SATA channels.

> Today basically all boards have also a PIRQ router that is used to map
> these PCI interrupt wires down into PIC interrupt inputs for when the
> system is in PIC compatibility mode (eg. when running the booter). 
> Sometimes they can also re-map interrupt lines in IO-APIC mode.

Ah, that sounds interesting.

> Since your system is running in ACPI mode, the output of acpidmp is
> needed to figure out exactly that the BIOS is saying the board can do.
> The output of lspci -l with this will tell us if we can split apart the
> SATA interrupts, or if they're wired together.

Hmm. I got pciutils 2.1.11 (those claim to be the latest), but my
lspci doesn't know "-l". I attached the output of lspci -vvv to this
mail, however. Maybe it's of any use.

I attached the output of acpidmp to this mail as well. It's a
collection of hexdumps. Since I have no internal knowledge about ACPI
or IO-APICs, I can't do anything with it...

> Another twist is that sometimes enabling/disabling devices in the BIOS
> SETUP will change how the BIOS configures the hardware and make more
> interrupts available.  Here, for example, USB seems to be low hanging
> fruit on a high-rent >= 16 IRQ.

Sorry, I didn't quite understand your last sentence with the fruits
and the rent. I suppose it's some expression, but I'm not a native
english speaker.

But I already disabled everything I don't need in the BIOS (I need
USB, however) and the situation didn't improve very dramatically. At
least I can't see of any devices having changed place in the IRQ list,
only that the devices I deactivated have gone. I also enable "Reset
ESCD data" in the BIOS to encourage things getting rearranged.

> If you're not using ACPI features, you might also try booting with
> "acpi=off" and see if the chip-set PIRQ router does a better job for
> you.

Hmm. If I remember correctly the IRQs stay XT-PIC if I don't enable
ACPI, regardless wether IO-APIC is enabled or not. And the old style
PIC of course leads to the result of my interrupts being very

Thanks for your help!

  reply	other threads:[~2003-12-08 20:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2003-12-08 19:29 ` balance interrupts Len Brown
2003-12-08 20:00   ` Julien Oster [this message]
2003-12-08 20:02     ` Julien Oster
2003-12-08 21:46     ` Len Brown
2003-12-09  3:51   ` Bob
2003-12-09  5:11     ` Stephen Satchell
2003-12-09 13:19     ` Swap performance statistics in 2.6 -- which /proc file has it? Stephen Satchell
2003-12-09 13:56       ` Richard B. Johnson
2003-12-09 14:46         ` Stephen Satchell
2003-12-09 15:25           ` Richard B. Johnson
2003-12-09 19:53             ` Dominik Kubla
2003-12-09 20:24               ` Richard B. Johnson
2003-12-10 10:18                 ` Dominik Kubla
2003-12-10  1:28               ` Stephen Satchell
2003-12-10 10:34                 ` Dominik Kubla
2003-12-10 13:06                   ` Answer to Swap performance statistics in 2.6 -- which /proc file has it Stephen Satchell
2003-12-08 17:59 balance interrupts Julien Oster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).