[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BAE9DCEF64577A439B3A37F36F9B691C02B81AAF@orsmsx418.amr.corp.intel.com>
Date: Fri, 20 Jul 2007 14:13:15 -0700
From: "Nelson, Shannon" <shannon.nelson@...el.com>
To: "Roland Dreier" <rdreier@...co.com>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
Cc: <akpm@...ux-foundation.org>, <linux-kernel@...r.kernel.org>,
<davem@...emloft.net>, <jeff@...zik.org>,
"Williams, Dan J" <dan.j.williams@...el.com>,
"Leech, Christopher" <christopher.leech@...el.com>
Subject: RE: [PATCH 5/7] I/OAT: Add support for MSI and MSI-X
Roland Dreier [mailto:rdreier@...co.com]
>
>OK, let's try to avoid going off into the weeds here. In the context
>of the specific patch that this thread started with, is there any
>point in having both "msix-single-vector" and "msi" interrupt support?
Some versions of this hardware support MSI-X and not MSI. If it can't
get all the MSI-X interrupts, it will try a single interrupt before
fallign all the way down to Legacy interrupts. Basically, if we can
only get one interrupt, we'd still like to use the MSI-X mechanics if
possible. If totally out of the question, then we'll use legacy.
sln
--
======================================================================
Mr. Shannon Nelson LAN Access Division, Intel Corp.
Shannon.Nelson@...el.com I don't speak for Intel
(503) 712-7659 Parents can't afford to be squeamish.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists