linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florin Andrei <florin@andrei.myip.org>
To: linux-kernel@vger.kernel.org
Subject: Re: generic method to assign IRQs
Date: 15 Jun 2003 15:26:56 -0700	[thread overview]
Message-ID: <1055716016.2808.33.camel@rivendell.home.local> (raw)
In-Reply-To: <Pine.LNX.4.33.0306140035560.29854-100000@router.windsormachine.com>

On Fri, 2003-06-13 at 21:37, Mike Dresser wrote:
> On 13 Jun 2003, Florin Andrei wrote:
> 
> > This issue may not matter much on "normal" systems, but it matters a
> > whole bunch on multimedia machines. Not being able to untangle like five
> > or six devices assigned to the same IRQ may render an otherwise powerful
> > system totally unusable for any decent media purpose (i'm talking here
> > about simple tasks such as watching movies, not necessarily of
> > professional stuff, which is even more demanding).
> 
> Some of the problem is that motherboard manufacturers setup their hardware
> so that slots HAVE to share IRQ's no matter what you do.  I've seen
> motherboards that have shared IRQ's even if there are no cards plugged in.

I think i see what you mean.

Still, then what's the explanation for this thing: if i run a non-APIC
kernel, lots of devices are on the same IRQ. Just enable APIC in the
kernel, and change nothing else, and the busy IRQ becomes less busy.
In either case, there are tons of spare IRQs, which just sit there idle,
unused.

If the problem would be entirely in hardware, i would say APIC shouldn't
make a big difference.

Do i miss something?

-- 
Florin Andrei

http://florin.myip.org/


      parent reply	other threads:[~2003-06-15 22:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-14  4:12 generic method to assign IRQs Florin Andrei
2003-06-14  4:37 ` Mike Dresser
2003-06-14  4:39   ` Trever L. Adams
2003-06-15 22:26   ` Florin Andrei [this message]

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=1055716016.2808.33.camel@rivendell.home.local \
    --to=florin@andrei.myip.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).