From: Roland Dreier <rdreier@cisco.com>
To: Andi Kleen <ak@suse.de>
Cc: Greg KH <gregkh@suse.de>, Dave Olson <olson@unixfolk.com>,
discuss@x86-64.org, Brice Goglin <brice@myri.com>,
linux-kernel@vger.kernel.org,
Greg Lindahl <greg.lindahl@qlogic.com>
Subject: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilitiesKJ
Date: Tue, 20 Jun 2006 15:46:55 -0700 [thread overview]
Message-ID: <adasllzmom8.fsf@cisco.com> (raw)
In-Reply-To: <200606210033.35409.ak@suse.de> (Andi Kleen's message of "Wed, 21 Jun 2006 00:33:35 +0200")
> NForce4 PCI Express is an unknown - we'll see how that works.
I have systems (HP DL145) with
PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
and MSI-X works fine for me with Mellanox PCIe adapters (with no
quirks or anything -- the BIOS enables it by default):
$ grep MSI-X /proc/interrupts
66: 205792 0 0 0 PCI-MSI-X ib_mthca (comp)
74: 1 0 0 0 PCI-MSI-X ib_mthca (async)
82: 1343 0 0 0 PCI-MSI-X ib_mthca (cmd)
- R.
next prev parent reply other threads:[~2006-06-20 22:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.5FgZbVFZIyOdjQ3utdNvbqTrUq0@ifi.uio.no>
[not found] ` <fa.URgTUhhO9H/aLp98XyIN2gzSppk@ifi.uio.no>
2006-06-20 5:42 ` [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities Dave Olson
2006-06-20 7:25 ` Andi Kleen
2006-06-20 8:02 ` Jeff Garzik
2006-06-20 8:13 ` Andi Kleen
2006-06-20 8:27 ` Jeff Garzik
2006-06-20 22:44 ` Eric W. Biederman
2006-06-20 20:03 ` Greg Lindahl
2006-06-20 20:20 ` Randy.Dunlap
2006-06-20 20:26 ` Brice Goglin
2006-06-20 20:41 ` Greg Lindahl
2006-06-20 20:50 ` Brice Goglin
2006-06-20 20:53 ` Jeff Garzik
2006-06-20 20:57 ` Dave Olson
2006-06-20 20:23 ` Roland Dreier
2006-06-20 20:54 ` Jeff Garzik
2006-06-20 21:29 ` Greg KH
2006-06-20 22:27 ` Brice Goglin
2006-06-20 23:05 ` Greg KH
2006-06-20 23:16 ` Brice Goglin
2006-06-20 22:33 ` [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilitiesKJ Andi Kleen
2006-06-20 22:46 ` Roland Dreier [this message]
2006-06-21 6:19 ` Dave Olson
2006-06-21 4:42 Allen Martin
2006-06-21 10:05 ` Andi Kleen
2006-06-21 16:21 ` Dave Olson
2006-06-21 16:37 ` Andi Kleen
[not found] ` <20060622012339.GD2614@greglaptop.internal.keyresearch.com>
2006-06-22 1:32 ` Greg Lindahl
-- strict thread matches above, loose matches on Subject: below --
2006-06-23 15:43 Naren (Narendra) Sankar
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=adasllzmom8.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=ak@suse.de \
--cc=brice@myri.com \
--cc=discuss@x86-64.org \
--cc=greg.lindahl@qlogic.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olson@unixfolk.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