From patchwork Wed Dec 17 16:58:26 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: "De Lara Guarch, Pablo" X-Patchwork-Id: 2070 Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [IPv6:::1]) by dpdk.org (Postfix) with ESMTP id 88963807E; Wed, 17 Dec 2014 17:58:53 +0100 (CET) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 629328054 for ; Wed, 17 Dec 2014 17:58:35 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 17 Dec 2014 08:56:55 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.07,595,1413270000"; d="scan'208";a="655717214" Received: from irvmail001.ir.intel.com ([163.33.26.43]) by orsmga002.jf.intel.com with ESMTP; 17 Dec 2014 08:58:33 -0800 Received: from sivswdev02.ir.intel.com (sivswdev02.ir.intel.com [10.237.217.46]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id sBHGwWAW020460; Wed, 17 Dec 2014 16:58:32 GMT Received: from sivswdev02.ir.intel.com (localhost [127.0.0.1]) by sivswdev02.ir.intel.com with ESMTP id sBHGwWlV013565; Wed, 17 Dec 2014 16:58:32 GMT Received: (from pdelarax@localhost) by sivswdev02.ir.intel.com with id sBHGwWcs013561; Wed, 17 Dec 2014 16:58:32 GMT From: Pablo de Lara To: dev@dpdk.org Date: Wed, 17 Dec 2014 16:58:26 +0000 Message-Id: <1418835507-13313-8-git-send-email-pablo.de.lara.guarch@intel.com> X-Mailer: git-send-email 1.7.4.1 In-Reply-To: <1418835507-13313-1-git-send-email-pablo.de.lara.guarch@intel.com> References: <1418741302-19898-1-git-send-email-siobhan.a.butler@intel.com> <1418835507-13313-1-git-send-email-pablo.de.lara.guarch@intel.com> MIME-Version: 1.0 Subject: [dpdk-dev] =?utf-8?q?=5BPATCH_v4_7/8=5D_doc=3A_updated_resolved_i?= =?utf-8?q?ssues_with_old_known_issues?= X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" From: Siobhan Butler Removed resolved issues from known issues section. Added new resolved issues to resolved issues section. Signed-off-by: Siobhan Butler --- doc/guides/rel_notes/known_issues.rst | 225 ------------------------------- doc/guides/rel_notes/resolved_issues.rst | 171 +++++++++++++++++++++++ 2 files changed, 171 insertions(+), 225 deletions(-) diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst index 0107f9d..3993b05 100644 --- a/doc/guides/rel_notes/known_issues.rst +++ b/doc/guides/rel_notes/known_issues.rst @@ -62,147 +62,6 @@ Pause Frame Forwarding does not work properly on igb | | | +--------------------------------+--------------------------------------------------------------------------------------+ -Running TestPMD with SRIOV in Domain U may cause it to hang when XENVIRT switch is on -------------------------------------------------------------------------------------- - -+--------------------------------+--------------------------------------------------------------------------------------+ -| Title | Running TestPMD with SRIOV in Domain U may cause it to hang when XENVIRT switch is on| -| | | -+================================+======================================================================================+ -| Reference # | IXA00168949 | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Description | When TestPMD is run with only SRIOV port “./testpmd -c f -n 4 -- -i” , the following | -| | error occurs: | -| | | -| | PMD: gntalloc: ioctl error | -| | | -| | EAL: Error - exiting with code: 1 | -| | | -| | Cause: Creation of mbuf pool for socket 0 failed | -| | | -| | Then, alternately run SRIOV port and virtIO with testpmd: | -| | | -| | testpmd -c f -n 4 -- -i | -| | | -| | testpmd -c f -n 4 --use-dev="eth_xenvirt0" -- -i | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Implication | DomU will not be accessible after you repeat this action some times | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Resolution/ Workaround | Run testpmd with a "--total-num-mbufs=N(N<=3500)" | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Affected Environment/ Platform | Fedora 16, 64 bits + Xen hypervisor 4.2.3 + Domain 0 kernel 3.10.0 | -| | +Domain U kernel 3.6.11 | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Driver/Module | TestPMD Sample Application | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ - -Vhost-xen cannot detect Domain U application exit on Xen version 4.0.1 ----------------------------------------------------------------------- - -+--------------------------------+--------------------------------------------------------------------------------------+ -| Title | Vhost-xen cannot detect Domain U application exit on Xen 4.0.1. | -| | | -+================================+======================================================================================+ -| Reference # | IXA00168947 | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Description | When using DPDK applications on Xen 4.0.1, e.g. TestPMD Sample Application, | -| | on killing the application (e.g. killall testmd) vhost-switch cannot detect | -| | the domain U exited and does not free the Virtio device. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Implication | Virtio device not freed after application is killed when using vhost-switch on Xen | -| | 4.0.1 | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Resolution | | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Affected Environment/ Platform | Xen 4.0.1 | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Driver/Module | Vhost-switch | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ - -Virtio incorrect header length used if MSI-X is disabled by kernel driver -------------------------------------------------------------------------- - -+--------------------------------+--------------------------------------------------------------------------------------+ -| Title | Virtio incorrect header length used if MSI-X is disabled by kernel driver or | -| | if VIRTIO_NET_F_MAC is not negotiated. | -| | | -+================================+======================================================================================+ -| Reference # | IXA00384256 | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Description | The Virtio header for host-guest communication is of variable length and | -| | is dependent on whether MSI-X has been enabled by the kernel driver for the network | -| | device. | -| | | -| | The base header length of 20 bytes will be extended by 4 bytes to accommodate MSI-X | -| | vectors and the Virtio Network Device header will appear at byte offset 24. | -| | | -| | The Userspace Virtio Poll Mode Driver tests the guest feature bits for the presence | -| | of VIRTIO_PCI_FLAG_MISIX, however this bit field is not part of the Virtio | -| | specification and resolves to the VIRTIO_NET_F_MAC feature instead. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Implication | The DPDK kernel driver will enable MSI-X by default, | -| | however if loaded with “intr_mode=legacy” on a guest with a Virtio Network Device, | -| | a KVM-Qemu guest may crash with the following error: “virtio-net header not in first | -| | element”. | -| | | -| | If VIRTIO_NET_F_MAC feature has not been negotiated, then the Userspace Poll Mode | -| | Driver will assume that MSI-X has been disabled and will prevent the proper | -| | functioning of the driver. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Resolution | Ensure #define VIRTIO_PCI_CONFIG(hw) returns the correct offset (20 or 24 bytes) for | -| | the devices where in rare cases MSI-X is disabled or VIRTIO_NET_F_MAC has not been | -| | negotiated. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Affected Environment/ Platform | Virtio devices where MSI-X is disabled or VIRTIO_NET_F_MAC feature has not been | -| | negotiated. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Driver/Module | librte_pmd_virtio | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ - -gmake clean may silently fail for some example applications ------------------------------------------------------------ - -+--------------------------------+--------------------------------------------------------------------------------------+ -| Title | When using Free BSD* 9.2 gmake clean may silently fail for some sample applications | -| | | -+================================+======================================================================================+ -| Reference # | IXA00834605 | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Description | gmake clean may silently fail leaving the source object files intact. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Implication | Application object files are not removed. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Resolution | Manually remove ./build folders or rebuild application source after editing. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Affected Environment/ Platform | FreeBSD* 9.2 and below | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Driver/Module | Example Applications | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ - In packets provided by the PMD, some flags are missing ------------------------------------------------------ @@ -415,35 +274,6 @@ Multi-process sample app requires exact memory mapping | | | +--------------------------------+--------------------------------------------------------------------------------------+ -Unstable system performance across application executions with 2MB pages ------------------------------------------------------------------------- - -+--------------------------------+--------------------------------------------------------------------------------------+ -| Title | Unstable system performance across application executions with 2MB pages | -| | | -+================================+======================================================================================+ -| Reference # | IXA00372346 | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Description | The performance of a DPDK application may vary across executions of an | -| | application due to a varying number of TLB misses depending on the location of | -| | accessed structures in memory. | -| | This situation occurs on rare occasions. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Implication | Occasionally, relatively poor performance of DPDK applications is encountered. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Resolution/ Workaround | Using 1 GB pages results in lower usage of TLB entries, resolving this issue. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Affected Environment/ Platform | Systems using 2 MB pages | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Driver/Module | All | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ - Packets are not sent by the 1 GbE/10 GbE SR-IOV driver when the source MAC address is not the MAC address assigned to the VF NIC -------------------------------------------------------------------------------------------------------------------------------- @@ -617,33 +447,6 @@ Kernel crash on IGB port unbinding | | | +--------------------------------+--------------------------------------------------------------------------------------+ -Link status change not working with MSI interrupts --------------------------------------------------- - -+--------------------------------+--------------------------------------------------------------------------------------+ -| Title | Link status change not working with MSI interrupts | -| | | -+================================+======================================================================================+ -| Reference # | IXA00378191 | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Description | MSI interrupts are not supported by the PMD. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Implication | Link status change will only work with legacy or MSI-X interrupts. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Resolution/ Workaround | The igb_uio driver can now be loaded with either legacy or MSI-X interrupt support. | -| | However, this configuration is not tested. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Affected Environment/ Platform | All | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Driver/Module | Poll Mode Driver (PMD) | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ - Twinpond and Ironpond NICs do not report link status correctly -------------------------------------------------------------- @@ -821,34 +624,6 @@ Differences in how different Intel NICs handle maximum packet length for jumbo f | | | +--------------------------------+--------------------------------------------------------------------------------------+ -Link status interrupt not working in VF drivers ------------------------------------------------ - -+--------------------------------+--------------------------------------------------------------------------------------+ -| Title | Link status interrupts not working in the VF drivers | -| | | -+================================+======================================================================================+ -| Reference | IXA00381312 | -| # | | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Description | Due to the driver not setting up interrupts for VF drivers, the NIC does not report | -| | link status change to VF devices. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Implication | Link status interrupts will not work in VM guests. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Resolution/ Workaround | There is no workaround available. | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Affected Environment/ Platform | All | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ -| Driver/Module | VF (SR-IOV) Poll Mode Driver (PMD) | -| | | -+--------------------------------+--------------------------------------------------------------------------------------+ - Binding PCI devices to igb_uio fails on Linux* kernel 3.9 when more than one device is used ------------------------------------------------------------------------------------------- diff --git a/doc/guides/rel_notes/resolved_issues.rst b/doc/guides/rel_notes/resolved_issues.rst index 16e1026..85ce566 100644 --- a/doc/guides/rel_notes/resolved_issues.rst +++ b/doc/guides/rel_notes/resolved_issues.rst @@ -33,6 +33,177 @@ Resolved Issues This section describes previously known issues that have been resolved since release version 1.2. +Running TestPMD with SRIOV in Domain U may cause it to hang when XENVIRT switch is on +------------------------------------------------------------------------------------- + ++--------------------------------+--------------------------------------------------------------------------------------+ +| Title | Running TestPMD with SRIOV in Domain U may cause it to hang when XENVIRT switch is on| +| | | ++================================+======================================================================================+ +| Reference # | IXA00168949 | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Description | When TestPMD is run with only SRIOV port /testpmd -c f -n 4 -- -i, the following | +| | error occurs: | +| | | +| | PMD: gntalloc: ioctl error | +| | | +| | EAL: Error - exiting with code: 1 | +| | | +| | Cause: Creation of mbuf pool for socket 0 failed | +| | | +| | Then, alternately run SRIOV port and virtIO with testpmd: | +| | | +| | testpmd -c f -n 4 -- -i | +| | | +| | testpmd -c f -n 4 --use-dev="eth_xenvirt0" -- -i | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Implication | DomU will not be accessible after you repeat this action some times | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Resolution/ Workaround | Run testpmd with a "--total-num-mbufs=N(N<=3500)" | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Affected Environment/ Platform | Fedora 16, 64 bits + Xen hypervisor 4.2.3 + Domain 0 kernel 3.10.0 | +| | +Domain U kernel 3.6.11 | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Driver/Module | TestPMD Sample Application | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ + +Vhost-xen cannot detect Domain U application exit on Xen version 4.0.1 +---------------------------------------------------------------------- + ++--------------------------------+--------------------------------------------------------------------------------------+ +| Title | Vhost-xen cannot detect Domain U application exit on Xen 4.0.1. | +| | | ++================================+======================================================================================+ +| Reference # | IXA00168947 | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Description | When using DPDK applications on Xen 4.0.1, e.g. TestPMD Sample Application, | +| | on killing the application (e.g. killall testmd) vhost-switch cannot detect | +| | the domain U exited and does not free the Virtio device. | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Implication | Virtio device not freed after application is killed when using vhost-switch on Xen | +| | 4.0.1 | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Resolution | Resolved in DPDK 1.8 | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Affected Environment/ Platform | Xen 4.0.1 | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Driver/Module | Vhost-switch | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ + +Virtio incorrect header length used if MSI-X is disabled by kernel driver +------------------------------------------------------------------------- + ++--------------------------------+--------------------------------------------------------------------------------------+ +| Title | Virtio incorrect header length used if MSI-X is disabled by kernel driver or | +| | if VIRTIO_NET_F_MAC is not negotiated. | +| | | ++================================+======================================================================================+ +| Reference # | IXA00384256 | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Description | The Virtio header for host-guest communication is of variable length and | +| | is dependent on whether MSI-X has been enabled by the kernel driver for the network | +| | device. | +| | | +| | The base header length of 20 bytes will be extended by 4 bytes to accommodate MSI-X | +| | vectors and the Virtio Network Device header will appear at byte offset 24. | +| | | +| | The Userspace Virtio Poll Mode Driver tests the guest feature bits for the presence | +| | of VIRTIO_PCI_FLAG_MISIX, however this bit field is not part of the Virtio | +| | specification and resolves to the VIRTIO_NET_F_MAC feature instead. | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Implication | The DPDK kernel driver will enable MSI-X by default, | +| | however if loaded with "intr_mode=legacy" on a guest with a Virtio Network Device, | +| | a KVM-Qemu guest may crash with the following error: "virtio-net header not in first | +| | element". | +| | | +| | If VIRTIO_NET_F_MAC feature has not been negotiated, then the Userspace Poll Mode | +| | Driver will assume that MSI-X has been disabled and will prevent the proper | +| | functioning of the driver. | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Resolution | Ensure #define VIRTIO_PCI_CONFIG(hw) returns the correct offset (20 or 24 bytes) for | +| | the devices where in rare cases MSI-X is disabled or VIRTIO_NET_F_MAC has not been | +| | negotiated. | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Affected Environment/ Platform | Virtio devices where MSI-X is disabled or VIRTIO_NET_F_MAC feature has not been | +| | negotiated. | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Driver/Module | librte_pmd_virtio | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ + +Unstable system performance across application executions with 2MB pages +------------------------------------------------------------------------ + ++--------------------------------+--------------------------------------------------------------------------------------+ +| Title | Unstable system performance across application executions with 2MB pages | +| | | ++================================+======================================================================================+ +| Reference # | IXA00372346 | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Description | The performance of an DPDK application may vary across executions of an | +| | application due to a varying number of TLB misses depending on the location of | +| | accessed structures in memory. | +| | This situation occurs on rare occasions. | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Implication | Occasionally, relatively poor performance of DPDK applications is encountered. | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Resolution/ Workaround | Using 1 GB pages results in lower usage of TLB entries, resolving this issue. | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Affected Environment/ Platform | Systems using 2 MB pages | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Driver/Module | All | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ + +Link status change not working with MSI interrupts +-------------------------------------------------- + ++--------------------------------+--------------------------------------------------------------------------------------+ +| Title | Link status change not working with MSI interrupts | +| | | ++================================+======================================================================================+ +| Reference # | IXA00378191 | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Description | MSI interrupts are not supported by the PMD. | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Implication | Link status change will only work with legacy or MSI-X interrupts. | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Resolution/ Workaround | The igb_uio driver can now be loaded with either legacy or MSI-X interrupt support. | +| | However, this configuration is not tested. | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Affected Environment/ Platform | All | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ +| Driver/Module | Poll Mode Driver (PMD) | +| | | ++--------------------------------+--------------------------------------------------------------------------------------+ + KNI does not provide Ethtool support for all NICs supported by the Poll-Mode Drivers ------------------------------------------------------------------------------------