From mboxrd@z Thu Jan 1 00:00:00 1970 From: heiner.kallweit@web.de (Heiner Kallweit) Date: Mon, 27 Oct 2014 20:38:04 +0100 Subject: Setting cpu affinity for MSI-X on i.mx6 possible? In-Reply-To: References: <544D37F7.2060800@web.de> <1414399977.2421.1.camel@pengutronix.de> <544E99FD.5040306@web.de> Message-ID: <544E9F1C.205@web.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Am 27.10.2014 um 20:31 schrieb Bjorn Helgaas: > On Mon, Oct 27, 2014 at 1:16 PM, Heiner Kallweit wrote: >> Thanks, Lucas. >> >> It's interesting however that the igb driver claims it's using MSI-X. >> Maybe the DW PCIE drivers offers MSI-X on the bus and just internally falls back to MSI? >> >> Rgds, Heiner >> >> [ 4.165850] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.2.15-k >> [ 4.172930] igb: Copyright (c) 2007-2014 Intel Corporation. >> [ 4.178638] igb 0000:01:00.0: enabling device (0140 -> 0142) >> [ 4.235789] igb 0000:01:00.0: added PHC on eth0 >> [ 4.235793] igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection >> [ 4.235799] igb 0000:01:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 00:01:c0:14:b1:58 >> [ 4.235804] igb 0000:01:00.0: eth0: PBA No: FFFFFF-0FF >> [ 4.235810] igb 0000:01:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s) > > What does "lspci -vvs01:00.0" say? It *looks* like igb pays attention > to whether enabling MSI-X worked, but that path in the driver is not > completely trivial, and I got tired of tracing the code to verify it. > > Bjorn > Thanks, Bjorn. Here comes the full output of the lspci command. [root at utilite ~]# lspci -vvs01:00.0 01:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) Subsystem: Intel Corporation Device 0000 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-