From: Tejun Heo <htejun@gmail.com>
To: Trent George <trent@norwalkdist.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: multiple irqs per card on the sata_sil24
Date: Wed, 27 Sep 2006 10:07:06 +0900 [thread overview]
Message-ID: <4519CEBA.90307@gmail.com> (raw)
In-Reply-To: <KMS--2046545466-1840@mail.norwalkdist.com>
Trent George wrote:
> While reading the specs, I noticed that the pci-x cards support splitting each port to a unique irq pin.
3124 doesn't seem to support multiple MSI interrupts either. Multiple
Message Capable field is 000b. Where does the spec say that it can
split each port to a unique irq pin?
> If you have 6 cards with 4 ports, can you spread the load over 24 irqs ?
> I dont know if the motherboard can support this, or the driver could be modified to do this.
> It would be nice when there is a lot of of disk traffic on lots of drives.... adding port multiplier drives to each channel.
> I am trying to build a VERY large duplication system using LOTS of bandwidth. the irq can really put stress on the system.
Theoretically, yes, but linux currently cannot do multiple MSI
interrupts and I don't think it's gonna be supported anytime soon.
pci-e + multiple MSIX interrupts are supported but AFAIK 3132 supports that.
sil24 is pretty efficient and it only takes one more register access to
determine which port has raised interrupt. Also, if you have multiple
busy ports w/ PMP attached, single interrupt is likely to serve multiple
ports, so I don't think it's gonna matter performance-wise.
> the final system would be 100+ drives all going over 22mb/s.
> It should give a nice supermicro board with 3 buses a real workout.
Impressive. Good luck and please keep us posted.
--
tejun
next prev parent reply other threads:[~2006-09-27 1:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 0:31 multiple irqs per card on the sata_sil24 Trent George
2006-09-27 0:46 ` Jeff Garzik
2006-09-27 1:07 ` Tejun Heo [this message]
2006-09-27 1:09 ` Tejun Heo
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=4519CEBA.90307@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=trent@norwalkdist.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).