From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 4369D23D for ; Mon, 15 Oct 2018 06:52:41 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Oct 2018 21:52:40 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,383,1534834800"; d="scan'208";a="97471525" Received: from dpdk-xiaoyunl.sh.intel.com ([10.67.110.231]) by fmsmga004.fm.intel.com with ESMTP; 14 Oct 2018 21:52:38 -0700 From: Xiaoyun Li To: beilei.xing@intel.com, qi.z.zhang@intel.com, dev@dpdk.org, wenzhuo.lu@intel.com, jingjing.wu@intel.com Cc: Xiaoyun Li Date: Mon, 15 Oct 2018 00:36:34 -0400 Message-Id: <1539578194-52527-1-git-send-email-xiaoyun.li@intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1538039797-43828-1-git-send-email-xiaoyun.li@intel.com> References: <1538039797-43828-1-git-send-email-xiaoyun.li@intel.com> Subject: [dpdk-dev] [PATCH v4] doc: add known issue about legacy intr mode for ixgbe X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2018 04:52:42 -0000 When using uio_pci_generic module or using legacy interrupt mode of igb_uio or vfio, X550 cannot get interrupts. Because the Interrupt Status bit is not implemented, then the irq cannot be handled correctly and cannot report the event fd to DPDK apps. Add this hw limitation and details into ixgbe known issue. Signed-off-by: Xiaoyun Li --- v4: * Clarify that the vfio workaround only works when the intx is not shared with other devices. v3: * Correct a misspelling. v2: * Correct the link of X550 spec update. * Polish the known issue title. --- doc/guides/nics/ixgbe.rst | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst index 16d6390..1c294b0 100644 --- a/doc/guides/nics/ixgbe.rst +++ b/doc/guides/nics/ixgbe.rst @@ -200,6 +200,33 @@ There is no RTE API to add a VF's MAC address from the PF. On ixgbe, the ``rte_eth_dev_mac_addr_add()`` function can be used to add a VF's MAC address, as a workaround. +X550 does not support legacy interrupt mode +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Desccription +^^^^^^^^^^^^ +X550 cannot get interrupts if using ``uio_pci_generic`` module or using legacy +interrupt mode of ``igb_uio`` or ``vfio``. Because the errata of X550 states +that the Interrupt Status bit is not implemented. The errata is the item #22 +from `X550 spec update `_ + +Implication +^^^^^^^^^^^ +When using ``uio_pci_generic`` module or using legacy interrupt mode of +``igb_uio`` or ``vfio``, the Interrupt Status bit would be checked if the +interrupt is coming. Since the bit is not implemented in X550, the irq cannot +be handled correctly and cannot report the event fd to DPDK apps. Then apps +cannot get interrupts and ``dmesg`` will show messages like ``irq #No.: `` +``nobody cared.`` + +Workaround +^^^^^^^^^^ +Do not bind the ``uio_pci_generic`` module in X550 NICs. +Do not bind ``igb_uio`` with legacy mode in X550 NICs. +Before binding ``vfio`` with legacy mode in X550 NICs, use ``modprobe vfio `` +``nointxmask=1`` to load ``vfio`` module if the intx is not shared with other +devices. Inline crypto processing support -------------------------------- -- 2.7.4