[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <D5C1322C3E673F459512FB59E0DDC32903445CD4@orsmsx414.amr.corp.intel.com>
Date: Fri, 20 Jul 2007 11:09:03 -0700
From: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
To: "Roland Dreier" <rdreier@...co.com>,
"Nelson, Shannon" <shannon.nelson@...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
> -----Original Message-----
> From: Roland Dreier [mailto:rdreier@...co.com]
> Sent: Friday, July 20, 2007 10:43 AM
> To: Nelson, Shannon
> Cc: akpm@...ux-foundation.org; linux-kernel@...r.kernel.org;
> davem@...emloft.net; jeff@...zik.org; Williams, Dan J; Leech,
> Christopher; Waskiewicz Jr, Peter P
> Subject: Re: [PATCH 5/7] I/OAT: Add support for MSI and MSI-X
>
> are there any devices that support MSI but not MSI-X? If
> not, is there any point in having code to support both?
>
> - R.
>
Both igb (recently posted) and ixgbe (also recently posted) support both
MSI and MSI-X. Right now when we try to request MSI-X vectors, if we
fail to acquire what we've asked for, we fall back to MSI support. If
MSI fails to initialize, we fall back to legacy interrupts. So it needs
to be there in case MSI-X allocation fails for the NIC driver.
Thanks,
-PJ Waskiewicz
-
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