public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Strand <bstrand@switchmanagement.com>
To: "Bonds, Deanna" <Deanna_Bonds@adaptec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3c59x + dpti2o problem with interrupt sharing?
Date: Tue, 25 Sep 2001 15:24:36 -0700	[thread overview]
Message-ID: <3BB10424.9070007@switchmanagement.com> (raw)
In-Reply-To: <50DB155AD0CED411988E009027D61DB324D507@otcexc01.otc.adaptec.com>

Bonds, Deanna wrote:

>>A related question is:  should these drivers be able to share 
>>IRQs, i.e. 
>>is it a worthwhile goal to have them operate reliably while sharing 
>>IRQs, or is IRQ-sharing a performance loss and something to 
>>be avoided?
>>
>
>The Adaptec card can share interrupts, but it is not wise to do that with
>another card that is going to be a high priority interrupt.  You most likely
>need to change the motherboard bios settings.  If you are not using your
>onboard IDE you can disable that freeing up another high priority interrupt.
>Otherwise you can manually assign the interrupts through the bios
>
I disabled onboard IDE (secondary channel; primary is needed for CDROM), 
serial, parallel, scsi, usb, and one of two onboard NICs, and now I am 
in a situation with no IRQ sharing.  Unfortunately this BIOS (Phoenix 
ServerBIOS 2 Rel 6.0, Tyan Thunder K7 BIOS v2.07a) does not allow me to 
assign IRQs to PCI slots, and I cannot move the RAID card around because 
it is in a 2U riser card.  Hopefully this will solve the problem.  On a 
broader note, where is the cause of this problem?  You indicated that 
the Adaptec card can share interrupts, so was the problem the 3com 
driver, the 3com hardware, the motherboard, or some other portion of the 
kernel?  It seems that given the scarcity of interrupts, this situation 
probably happens a lot, so we should handle it gracefully (meaning that 
I should go investigate the 3c59x and dpti2o drivers some more if it is 
a problem which is solvable in software).

Thanks,
Brian Strand



  reply	other threads:[~2001-09-25 22:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25 18:57 3c59x + dpti2o problem with interrupt sharing? Bonds, Deanna
2001-09-25 22:24 ` Brian Strand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-25  5:17 Brian Strand

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=3BB10424.9070007@switchmanagement.com \
    --to=bstrand@switchmanagement.com \
    --cc=Deanna_Bonds@adaptec.com \
    --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