| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <465A38B0.6030604@gmail.com> Date: Mon, 28 May 2007 06:04:32 +0400 From: Manu Abraham <abraham.manu@...il.com> To: Roland Dreier <rdreier@...co.com> CC: Grant Grundler <grundler@...isc-linux.org>, Greg KH <greg@...ah.com>, linux-pci@...ey.karlin.mff.cuni.cz, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: PCIE Roland Dreier wrote: > > >> Another question would be if the device supports multiple messages, MSIX > > >> should be used ? > > > > > > Yes. Assuming the device supports multiple MSI-X messages. > > At least on my device (PCI ID 1131:7162) there is no MSI-X capability, > so that's not an option for you. The current Linux implementation > does not support more than one MSI interrupt, so you just get one > interrupt with pci_enable_msi(). This would mean MSI or MSI-X ? A bit confused now. • MSI capability - 32 different messages - programmable ID in MSI message data field - programmable TC in MSI message address field - 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