From: Robert Hancock <hancockrwd@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Options: To use MSI-X or not?
Date: Wed, 04 Nov 2009 18:05:39 -0600 [thread overview]
Message-ID: <4AF216D3.4040903@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0911041151410.17867@p34.internal.lan>
On 11/04/2009 10:53 AM, Justin Piszcz wrote:
> Hello,
>
> I was curious whether its best to use MSI-X when the driver supports it
> or not?
>
> Example, 3ware cards/Intel Audio Drivers you can use MSI-X instead of
> having several devices use/share an interrupt.
>
> What are the pros/cons to using MSI-X vs. having devices share an IRQ?
Normally using MSI/MSI-X is always better (or at least no worse),
assuming it works properly on the system and on the device.. Hopefully
by this point we've fixed most or all the system-related problems or
forced MSI off on platforms where it can't work properly.
prev parent reply other threads:[~2009-11-05 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 16:53 Kernel Options: To use MSI-X or not? Justin Piszcz
2009-11-04 17:36 ` Valdis.Kletnieks
2009-11-05 0:04 ` Robert Hancock
2009-11-05 0:05 ` Robert Hancock [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=4AF216D3.4040903@gmail.com \
--to=hancockrwd@gmail.com \
--cc=jpiszcz@lucidpixels.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