From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Roger Heflin <rheflin@atipa.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: Re: What determines which interrupts are shared under Linux?
Date: Tue, 15 Aug 2006 16:06:19 +0100 [thread overview]
Message-ID: <1155654379.24077.286.camel@localhost.localdomain> (raw)
In-Reply-To: <44E1D760.6070600@atipa.com>
Ar Maw, 2006-08-15 am 09:17 -0500, ysgrifennodd Roger Heflin:
> On Linux when interrupts are defined similar to below, what defines say
> ide2, ide3 to be on the same interrupt? The bios, linux, the driver using
> the interrupt? And can that be controlled/overrode at the
> kernel/driver level?
Only with a soldering iron. They are the way the system is wired. Moving
boards between slots may change the IRQ allocation.
> I have identified that the disks that are shared on ide2, ide3 do funny
> things when both are being heavily used (dma_expiry), this is an older
> driver versions
That could be occuring just through lack of PCI bus bandwidth.
next prev parent reply other threads:[~2006-08-15 14:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 14:17 What determines which interrupts are shared under Linux? Roger Heflin
2006-08-15 14:30 ` Sergei Shtylyov
2006-08-15 14:38 ` Roger Heflin
2006-08-15 14:47 ` Len Brown
2006-08-15 15:06 ` Alan Cox [this message]
2006-08-15 15:24 ` Roger Heflin
2006-08-15 15:55 ` Alan Cox
2006-08-15 17:47 ` Roger Heflin
2006-08-15 18:13 ` Alan Cox
2006-08-16 22:54 ` Mark Lord
2006-08-17 0:39 ` Alan Cox
2006-08-17 13:18 ` Roger Heflin
2006-08-15 15:19 ` linux-os (Dick Johnson)
2006-08-15 17:31 ` Terence Ripperda
2006-08-15 17:42 ` Sergei Shtylyov
2006-08-15 17:43 ` Terence Ripperda
[not found] <fa.xiop2gho7OdOydmzXzpUsR5ksXM@ifi.uio.no>
2006-08-15 14:29 ` Robert Hancock
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1155654379.24077.286.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rheflin@atipa.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).