Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/2079/?format=api
{ "id": 2079, "url": "http://patchwork.dpdk.org/api/patches/2079/?format=api", "web_url": "http://patchwork.dpdk.org/project/dpdk/patch/1418834857-8643-8-git-send-email-pablo.de.lara.guarch@intel.com/", "project": { "id": 1, "url": "http://patchwork.dpdk.org/api/projects/1/?format=api", "name": "DPDK", "link_name": "dpdk", "list_id": "dev.dpdk.org", "list_email": "dev@dpdk.org", "web_url": "http://core.dpdk.org", "scm_url": "git://dpdk.org/dpdk", "webscm_url": "http://git.dpdk.org/dpdk", "list_archive_url": "https://inbox.dpdk.org/dev", "list_archive_url_format": "https://inbox.dpdk.org/dev/{}", "commit_url_format": "" }, "msgid": "<1418834857-8643-8-git-send-email-pablo.de.lara.guarch@intel.com>", "list_archive_url": "https://inbox.dpdk.org/dev/1418834857-8643-8-git-send-email-pablo.de.lara.guarch@intel.com", "date": "2014-12-17T16:47:36", "name": "[dpdk-dev,v4,7/8] doc: updated resolved issues with old known issues", "commit_ref": null, "pull_url": null, "state": "accepted", "archived": true, "hash": "693d630d6861e9fca757d38547b2aac21dffcb82", "submitter": { "id": 9, "url": "http://patchwork.dpdk.org/api/people/9/?format=api", "name": "De Lara Guarch, Pablo", "email": "pablo.de.lara.guarch@intel.com" }, "delegate": null, "mbox": "http://patchwork.dpdk.org/project/dpdk/patch/1418834857-8643-8-git-send-email-pablo.de.lara.guarch@intel.com/mbox/", "series": [], "comments": "http://patchwork.dpdk.org/api/patches/2079/comments/", "check": "pending", "checks": "http://patchwork.dpdk.org/api/patches/2079/checks/", "tags": {}, "related": [], "headers": { "Return-Path": "<dev-bounces@dpdk.org>", "X-Original-To": "patchwork@dpdk.org", "Delivered-To": "patchwork@dpdk.org", "Received": [ "from [92.243.14.124] (localhost [IPv6:::1])\n\tby dpdk.org (Postfix) with ESMTP id 98C4E7E6A;\n\tWed, 17 Dec 2014 18:07:46 +0100 (CET)", "from mga01.intel.com (mga01.intel.com [192.55.52.88])\n\tby dpdk.org (Postfix) with ESMTP id C20122A9\n\tfor <dev@dpdk.org>; Wed, 17 Dec 2014 18:07:43 +0100 (CET)", "from fmsmga002.fm.intel.com ([10.253.24.26])\n\tby fmsmga101.fm.intel.com with ESMTP; 17 Dec 2014 09:05:44 -0800", "from irvmail001.ir.intel.com ([163.33.26.43])\n\tby fmsmga002.fm.intel.com with ESMTP; 17 Dec 2014 09:05:43 -0800", "from sivswdev02.ir.intel.com (sivswdev02.ir.intel.com\n\t[10.237.217.46])\n\tby irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id\n\tsBHGlnet017970; Wed, 17 Dec 2014 16:47:49 GMT", "from sivswdev02.ir.intel.com (localhost [127.0.0.1])\n\tby sivswdev02.ir.intel.com with ESMTP id sBHGlnJn008845;\n\tWed, 17 Dec 2014 16:47:49 GMT", "(from pdelarax@localhost)\n\tby sivswdev02.ir.intel.com with id sBHGln3T008841;\n\tWed, 17 Dec 2014 16:47:49 GMT" ], "X-ExtLoop1": "1", "X-IronPort-AV": "E=Sophos;i=\"5.07,595,1413270000\"; d=\"scan'208\";a=\"649230976\"", "From": "Pablo de Lara <pablo.de.lara.guarch@intel.com>", "To": "dev@dpdk.org", "Date": "Wed, 17 Dec 2014 16:47:36 +0000", "Message-Id": "<1418834857-8643-8-git-send-email-pablo.de.lara.guarch@intel.com>", "X-Mailer": "git-send-email 1.7.4.1", "In-Reply-To": "<1418834857-8643-1-git-send-email-pablo.de.lara.guarch@intel.com>", "References": "<1418741302-19898-1-git-send-email-siobhan.a.butler@intel.com>\n\t<1418834857-8643-1-git-send-email-pablo.de.lara.guarch@intel.com>", "MIME-Version": "1.0", "Content-Type": "text/plain; charset=UTF-8", "Content-Transfer-Encoding": "8bit", "Subject": "[dpdk-dev] =?utf-8?q?=5BPATCH_v4_7/8=5D_doc=3A_updated_resolved_i?=\n\t=?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 <dev.dpdk.org>", "List-Unsubscribe": "<http://dpdk.org/ml/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>", "List-Archive": "<http://dpdk.org/ml/archives/dev/>", "List-Post": "<mailto:dev@dpdk.org>", "List-Help": "<mailto:dev-request@dpdk.org?subject=help>", "List-Subscribe": "<http://dpdk.org/ml/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>", "Errors-To": "dev-bounces@dpdk.org", "Sender": "\"dev\" <dev-bounces@dpdk.org>" }, "content": "From: Siobhan Butler <siobhan.a.butler@intel.com>\n\nRemoved resolved issues from known issues section.\nAdded new resolved issues to resolved issues section.\n\nSigned-off-by: Siobhan Butler <siobhan.a.butler@intel.com>\n---\n doc/guides/rel_notes/known_issues.rst | 225 -------------------------------\n doc/guides/rel_notes/resolved_issues.rst | 171 +++++++++++++++++++++++\n 2 files changed, 171 insertions(+), 225 deletions(-)", "diff": "diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst\nindex 0107f9d..3993b05 100644\n--- a/doc/guides/rel_notes/known_issues.rst\n+++ b/doc/guides/rel_notes/known_issues.rst\n@@ -62,147 +62,6 @@ Pause Frame Forwarding does not work properly on igb\n | | |\n +--------------------------------+--------------------------------------------------------------------------------------+\n \n-Running TestPMD with SRIOV in Domain U may cause it to hang when XENVIRT switch is on\n--------------------------------------------------------------------------------------\n-\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Title | Running TestPMD with SRIOV in Domain U may cause it to hang when XENVIRT switch is on|\n-| | |\n-+================================+======================================================================================+\n-| Reference # | IXA00168949 |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Description | When TestPMD is run with only SRIOV port “./testpmd -c f -n 4 -- -i” , the following |\n-| | error occurs: |\n-| | |\n-| | PMD: gntalloc: ioctl error |\n-| | |\n-| | EAL: Error - exiting with code: 1 |\n-| | |\n-| | Cause: Creation of mbuf pool for socket 0 failed |\n-| | |\n-| | Then, alternately run SRIOV port and virtIO with testpmd: |\n-| | |\n-| | testpmd -c f -n 4 -- -i |\n-| | |\n-| | testpmd -c f -n 4 --use-dev=\"eth_xenvirt0\" -- -i |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Implication | DomU will not be accessible after you repeat this action some times |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Resolution/ Workaround | Run testpmd with a \"--total-num-mbufs=N(N<=3500)\" |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Affected Environment/ Platform | Fedora 16, 64 bits + Xen hypervisor 4.2.3 + Domain 0 kernel 3.10.0 |\n-| | +Domain U kernel 3.6.11 |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Driver/Module | TestPMD Sample Application |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-\n-Vhost-xen cannot detect Domain U application exit on Xen version 4.0.1\n-----------------------------------------------------------------------\n-\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Title | Vhost-xen cannot detect Domain U application exit on Xen 4.0.1. |\n-| | |\n-+================================+======================================================================================+\n-| Reference # | IXA00168947 |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Description | When using DPDK applications on Xen 4.0.1, e.g. TestPMD Sample Application, |\n-| | on killing the application (e.g. killall testmd) vhost-switch cannot detect |\n-| | the domain U exited and does not free the Virtio device. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Implication | Virtio device not freed after application is killed when using vhost-switch on Xen |\n-| | 4.0.1 |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Resolution | |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Affected Environment/ Platform | Xen 4.0.1 |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Driver/Module | Vhost-switch |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-\n-Virtio incorrect header length used if MSI-X is disabled by kernel driver\n--------------------------------------------------------------------------\n-\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Title | Virtio incorrect header length used if MSI-X is disabled by kernel driver or |\n-| | if VIRTIO_NET_F_MAC is not negotiated. |\n-| | |\n-+================================+======================================================================================+\n-| Reference # | IXA00384256 |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Description | The Virtio header for host-guest communication is of variable length and |\n-| | is dependent on whether MSI-X has been enabled by the kernel driver for the network |\n-| | device. |\n-| | |\n-| | The base header length of 20 bytes will be extended by 4 bytes to accommodate MSI-X |\n-| | vectors and the Virtio Network Device header will appear at byte offset 24. |\n-| | |\n-| | The Userspace Virtio Poll Mode Driver tests the guest feature bits for the presence |\n-| | of VIRTIO_PCI_FLAG_MISIX, however this bit field is not part of the Virtio |\n-| | specification and resolves to the VIRTIO_NET_F_MAC feature instead. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Implication | The DPDK kernel driver will enable MSI-X by default, |\n-| | however if loaded with “intr_mode=legacy” on a guest with a Virtio Network Device, |\n-| | a KVM-Qemu guest may crash with the following error: “virtio-net header not in first |\n-| | element”. |\n-| | |\n-| | If VIRTIO_NET_F_MAC feature has not been negotiated, then the Userspace Poll Mode |\n-| | Driver will assume that MSI-X has been disabled and will prevent the proper |\n-| | functioning of the driver. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Resolution | Ensure #define VIRTIO_PCI_CONFIG(hw) returns the correct offset (20 or 24 bytes) for |\n-| | the devices where in rare cases MSI-X is disabled or VIRTIO_NET_F_MAC has not been |\n-| | negotiated. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Affected Environment/ Platform | Virtio devices where MSI-X is disabled or VIRTIO_NET_F_MAC feature has not been |\n-| | negotiated. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Driver/Module | librte_pmd_virtio |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-\n-gmake clean may silently fail for some example applications\n------------------------------------------------------------\n-\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Title | When using Free BSD* 9.2 gmake clean may silently fail for some sample applications |\n-| | |\n-+================================+======================================================================================+\n-| Reference # | IXA00834605 |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Description | gmake clean may silently fail leaving the source object files intact. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Implication | Application object files are not removed. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Resolution | Manually remove ./build folders or rebuild application source after editing. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Affected Environment/ Platform | FreeBSD* 9.2 and below |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Driver/Module | Example Applications |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-\n In packets provided by the PMD, some flags are missing\n ------------------------------------------------------\n \n@@ -415,35 +274,6 @@ Multi-process sample app requires exact memory mapping\n | | |\n +--------------------------------+--------------------------------------------------------------------------------------+\n \n-Unstable system performance across application executions with 2MB pages\n-------------------------------------------------------------------------\n-\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Title | Unstable system performance across application executions with 2MB pages |\n-| | |\n-+================================+======================================================================================+\n-| Reference # | IXA00372346 |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Description | The performance of a DPDK application may vary across executions of an |\n-| | application due to a varying number of TLB misses depending on the location of |\n-| | accessed structures in memory. |\n-| | This situation occurs on rare occasions. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Implication | Occasionally, relatively poor performance of DPDK applications is encountered. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Resolution/ Workaround | Using 1 GB pages results in lower usage of TLB entries, resolving this issue. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Affected Environment/ Platform | Systems using 2 MB pages |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Driver/Module | All |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-\n 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\n --------------------------------------------------------------------------------------------------------------------------------\n \n@@ -617,33 +447,6 @@ Kernel crash on IGB port unbinding\n | | |\n +--------------------------------+--------------------------------------------------------------------------------------+\n \n-Link status change not working with MSI interrupts\n---------------------------------------------------\n-\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Title | Link status change not working with MSI interrupts |\n-| | |\n-+================================+======================================================================================+\n-| Reference # | IXA00378191 |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Description | MSI interrupts are not supported by the PMD. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Implication | Link status change will only work with legacy or MSI-X interrupts. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Resolution/ Workaround | The igb_uio driver can now be loaded with either legacy or MSI-X interrupt support. |\n-| | However, this configuration is not tested. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Affected Environment/ Platform | All |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Driver/Module | Poll Mode Driver (PMD) |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-\n Twinpond and Ironpond NICs do not report link status correctly\n --------------------------------------------------------------\n \n@@ -821,34 +624,6 @@ Differences in how different Intel NICs handle maximum packet length for jumbo f\n | | |\n +--------------------------------+--------------------------------------------------------------------------------------+\n \n-Link status interrupt not working in VF drivers\n------------------------------------------------\n-\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Title | Link status interrupts not working in the VF drivers |\n-| | |\n-+================================+======================================================================================+\n-| Reference | IXA00381312 |\n-| # | |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Description | Due to the driver not setting up interrupts for VF drivers, the NIC does not report |\n-| | link status change to VF devices. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Implication | Link status interrupts will not work in VM guests. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Resolution/ Workaround | There is no workaround available. |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Affected Environment/ Platform | All |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-| Driver/Module | VF (SR-IOV) Poll Mode Driver (PMD) |\n-| | |\n-+--------------------------------+--------------------------------------------------------------------------------------+\n-\n Binding PCI devices to igb_uio fails on Linux* kernel 3.9 when more than one device is used\n -------------------------------------------------------------------------------------------\n \ndiff --git a/doc/guides/rel_notes/resolved_issues.rst b/doc/guides/rel_notes/resolved_issues.rst\nindex 16e1026..85ce566 100644\n--- a/doc/guides/rel_notes/resolved_issues.rst\n+++ b/doc/guides/rel_notes/resolved_issues.rst\n@@ -33,6 +33,177 @@ Resolved Issues\n \n This section describes previously known issues that have been resolved since release version 1.2.\n \n+Running TestPMD with SRIOV in Domain U may cause it to hang when XENVIRT switch is on\n+-------------------------------------------------------------------------------------\n+\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Title | Running TestPMD with SRIOV in Domain U may cause it to hang when XENVIRT switch is on|\n+| | |\n++================================+======================================================================================+\n+| Reference # | IXA00168949 |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Description | When TestPMD is run with only SRIOV port /testpmd -c f -n 4 -- -i, the following |\n+| | error occurs: |\n+| | |\n+| | PMD: gntalloc: ioctl error |\n+| | |\n+| | EAL: Error - exiting with code: 1 |\n+| | |\n+| | Cause: Creation of mbuf pool for socket 0 failed |\n+| | |\n+| | Then, alternately run SRIOV port and virtIO with testpmd: |\n+| | |\n+| | testpmd -c f -n 4 -- -i |\n+| | |\n+| | testpmd -c f -n 4 --use-dev=\"eth_xenvirt0\" -- -i |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Implication | DomU will not be accessible after you repeat this action some times |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Resolution/ Workaround | Run testpmd with a \"--total-num-mbufs=N(N<=3500)\" |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Affected Environment/ Platform | Fedora 16, 64 bits + Xen hypervisor 4.2.3 + Domain 0 kernel 3.10.0 |\n+| | +Domain U kernel 3.6.11 |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Driver/Module | TestPMD Sample Application |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+\n+Vhost-xen cannot detect Domain U application exit on Xen version 4.0.1\n+----------------------------------------------------------------------\n+\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Title | Vhost-xen cannot detect Domain U application exit on Xen 4.0.1. |\n+| | |\n++================================+======================================================================================+\n+| Reference # | IXA00168947 |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Description | When using DPDK applications on Xen 4.0.1, e.g. TestPMD Sample Application, |\n+| | on killing the application (e.g. killall testmd) vhost-switch cannot detect |\n+| | the domain U exited and does not free the Virtio device. |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Implication | Virtio device not freed after application is killed when using vhost-switch on Xen |\n+| | 4.0.1 |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Resolution | Resolved in DPDK 1.8 |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Affected Environment/ Platform | Xen 4.0.1 |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Driver/Module | Vhost-switch |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+\n+Virtio incorrect header length used if MSI-X is disabled by kernel driver\n+-------------------------------------------------------------------------\n+\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Title | Virtio incorrect header length used if MSI-X is disabled by kernel driver or |\n+| | if VIRTIO_NET_F_MAC is not negotiated. |\n+| | |\n++================================+======================================================================================+\n+| Reference # | IXA00384256 |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Description | The Virtio header for host-guest communication is of variable length and |\n+| | is dependent on whether MSI-X has been enabled by the kernel driver for the network |\n+| | device. |\n+| | |\n+| | The base header length of 20 bytes will be extended by 4 bytes to accommodate MSI-X |\n+| | vectors and the Virtio Network Device header will appear at byte offset 24. |\n+| | |\n+| | The Userspace Virtio Poll Mode Driver tests the guest feature bits for the presence |\n+| | of VIRTIO_PCI_FLAG_MISIX, however this bit field is not part of the Virtio |\n+| | specification and resolves to the VIRTIO_NET_F_MAC feature instead. |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Implication | The DPDK kernel driver will enable MSI-X by default, |\n+| | however if loaded with \"intr_mode=legacy\" on a guest with a Virtio Network Device, |\n+| | a KVM-Qemu guest may crash with the following error: \"virtio-net header not in first |\n+| | element\". |\n+| | |\n+| | If VIRTIO_NET_F_MAC feature has not been negotiated, then the Userspace Poll Mode |\n+| | Driver will assume that MSI-X has been disabled and will prevent the proper |\n+| | functioning of the driver. |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Resolution | Ensure #define VIRTIO_PCI_CONFIG(hw) returns the correct offset (20 or 24 bytes) for |\n+| | the devices where in rare cases MSI-X is disabled or VIRTIO_NET_F_MAC has not been |\n+| | negotiated. |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Affected Environment/ Platform | Virtio devices where MSI-X is disabled or VIRTIO_NET_F_MAC feature has not been |\n+| | negotiated. |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Driver/Module | librte_pmd_virtio |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+\n+Unstable system performance across application executions with 2MB pages\n+------------------------------------------------------------------------\n+\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Title | Unstable system performance across application executions with 2MB pages |\n+| | |\n++================================+======================================================================================+\n+| Reference # | IXA00372346 |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Description | The performance of an DPDK application may vary across executions of an |\n+| | application due to a varying number of TLB misses depending on the location of |\n+| | accessed structures in memory. |\n+| | This situation occurs on rare occasions. |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Implication | Occasionally, relatively poor performance of DPDK applications is encountered. |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Resolution/ Workaround | Using 1 GB pages results in lower usage of TLB entries, resolving this issue. |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Affected Environment/ Platform | Systems using 2 MB pages |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Driver/Module | All |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+\n+Link status change not working with MSI interrupts\n+--------------------------------------------------\n+\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Title | Link status change not working with MSI interrupts |\n+| | |\n++================================+======================================================================================+\n+| Reference # | IXA00378191 |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Description | MSI interrupts are not supported by the PMD. |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Implication | Link status change will only work with legacy or MSI-X interrupts. |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Resolution/ Workaround | The igb_uio driver can now be loaded with either legacy or MSI-X interrupt support. |\n+| | However, this configuration is not tested. |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Affected Environment/ Platform | All |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+| Driver/Module | Poll Mode Driver (PMD) |\n+| | |\n++--------------------------------+--------------------------------------------------------------------------------------+\n+\n KNI does not provide Ethtool support for all NICs supported by the Poll-Mode Drivers\n ------------------------------------------------------------------------------------\n \n", "prefixes": [ "dpdk-dev", "v4", "7/8" ] }