From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pablo de Lara Subject: =?utf-8?q?=5BPATCH_v4_7/8=5D_doc=3A_updated_resolved_i?= =?utf-8?q?ssues_with_old_known_issues?= Date: Wed, 17 Dec 2014 16:47:36 +0000 Message-ID: <1418834857-8643-8-git-send-email-pablo.de.lara.guarch@intel.com> References: <1418741302-19898-1-git-send-email-siobhan.a.butler@intel.com> <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: quoted-printable To: dev-VfR2kkLFssw@public.gmane.org Return-path: In-Reply-To: <1418834857-8643-1-git-send-email-pablo.de.lara.guarch-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.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 | | = | +--------------------------------+--------------------------------------= ------------------------------------------------+ =20 -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| -| | = | -+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ -| Reference # | IXA00168949 = | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Description | When TestPMD is run with only SRIOV p= ort =E2=80=9C./testpmd -c f -n 4 -- -i=E2=80=9D , the following | -| | error occurs: = | -| | = | -| | PMD: gntalloc: ioctl error = | -| | = | -| | EAL: Error - exiting with code: 1 = | -| | = | -| | Cause: Creation of mbuf pool for sock= et 0 failed | -| | = | -| | Then, alternately run SRIOV port and = virtIO with testpmd: | -| | = | -| | testpmd -c f -n 4 -- -i = | -| | = | -| | testpmd -c f -n 4 --use-dev=3D"eth_xe= nvirt0" -- -i | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Implication | DomU will not be accessible after you= repeat this action some times | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Resolution/ Workaround | Run testpmd with a "--total-num-mbufs= =3DN(N<=3D3500)" | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| 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 appl= ication exit on Xen 4.0.1. | -| | = | -+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ -| Reference # | IXA00168947 = | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Description | When using DPDK applications on Xen 4= .0.1, e.g. TestPMD Sample Application, | -| | on killing the application (e.g. kill= all testmd) vhost-switch cannot detect | -| | the domain U exited and does not free= the Virtio device. | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Implication | Virtio device not freed after applica= tion 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 drive= r -------------------------------------------------------------------------= - - -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Title | Virtio incorrect header length used i= f MSI-X is disabled by kernel driver or | -| | if VIRTIO_NET_F_MAC is not negotiated= . | -| | = | -+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ -| Reference # | IXA00384256 = | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Description | The Virtio header for host-guest comm= unication is of variable length and | -| | is dependent on whether MSI-X has bee= n enabled by the kernel driver for the network | -| | device. = | -| | = | -| | The base header length of 20 bytes wi= ll 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 thi= s bit field is not part of the Virtio | -| | specification and resolves to the VIR= TIO_NET_F_MAC feature instead. | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Implication | The DPDK kernel driver will enable MS= I-X by default, | -| | however if loaded with =E2=80=9Cintr_= mode=3Dlegacy=E2=80=9D on a guest with a Virtio Network Device, | -| | a KVM-Qemu guest may crash with the f= ollowing error: =E2=80=9Cvirtio-net header not in first | -| | element=E2=80=9D. = | -| | = | -| | If VIRTIO_NET_F_MAC feature has not b= een negotiated, then the Userspace Poll Mode | -| | Driver will assume that MSI-X has bee= n 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 disabl= ed 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 | -| | = | -+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ -| Reference # | IXA00834605 = | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Description | gmake clean may silently fail leaving= the source object files intact. | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Implication | Application object files are not remo= ved. | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Resolution | Manually remove ./build folders or re= build 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 ------------------------------------------------------ =20 @@ -415,35 +274,6 @@ Multi-process sample app requires exact memory mappi= ng | | = | +--------------------------------+--------------------------------------= ------------------------------------------------+ =20 -Unstable system performance across application executions with 2MB pages ------------------------------------------------------------------------- - -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Title | Unstable system performance across ap= plication executions with 2MB pages | -| | = | -+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ -| Reference # | IXA00372346 = | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Description | The performance of a DPDK application= may vary across executions of an | -| | application due to a varying number o= f TLB misses depending on the location of | -| | accessed structures in memory. = | -| | This situation occurs on rare occasio= ns. | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Implication | Occasionally, relatively poor perform= ance of DPDK applications is encountered. | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Resolution/ Workaround | Using 1 GB pages results in lower usa= ge 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 M= AC address is not the MAC address assigned to the VF NIC ------------------------------------------------------------------------= -------------------------------------------------------- =20 @@ -617,33 +447,6 @@ Kernel crash on IGB port unbinding | | = | +--------------------------------+--------------------------------------= ------------------------------------------------+ =20 -Link status change not working with MSI interrupts --------------------------------------------------- - -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Title | Link status change not working with M= SI interrupts | -| | = | -+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ -| Reference # | IXA00378191 = | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Description | MSI interrupts are not supported by t= he PMD. | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Implication | Link status change will only work wit= h 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 te= sted. | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Affected Environment/ Platform | All = | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Driver/Module | Poll Mode Driver (PMD) = | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ - Twinpond and Ironpond NICs do not report link status correctly -------------------------------------------------------------- =20 @@ -821,34 +624,6 @@ Differences in how different Intel NICs handle maxim= um packet length for jumbo f | | = | +--------------------------------+--------------------------------------= ------------------------------------------------+ =20 -Link status interrupt not working in VF drivers ------------------------------------------------ - -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Title | Link status interrupts not working in= the VF drivers | -| | = | -+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ -| Reference | IXA00381312 = | -| # | = | -| | = | -+--------------------------------+--------------------------------------= ------------------------------------------------+ -| Description | Due to the driver not setting up inte= rrupts 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 ------------------------------------------------------------------------= ------------------- =20 diff --git a/doc/guides/rel_notes/resolved_issues.rst b/doc/guides/rel_no= tes/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 =20 This section describes previously known issues that have been resolved s= ince release version 1.2. =20 +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| +| | = | ++=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ +| Reference # | IXA00168949 = | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Description | When TestPMD is run with only SRIOV p= ort /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 sock= et 0 failed | +| | = | +| | Then, alternately run SRIOV port and = virtIO with testpmd: | +| | = | +| | testpmd -c f -n 4 -- -i = | +| | = | +| | testpmd -c f -n 4 --use-dev=3D"eth_xe= nvirt0" -- -i | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Implication | DomU will not be accessible after you= repeat this action some times | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Resolution/ Workaround | Run testpmd with a "--total-num-mbufs= =3DN(N<=3D3500)" | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| 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 appl= ication exit on Xen 4.0.1. | +| | = | ++=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ +| Reference # | IXA00168947 = | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Description | When using DPDK applications on Xen 4= .0.1, e.g. TestPMD Sample Application, | +| | on killing the application (e.g. kill= all testmd) vhost-switch cannot detect | +| | the domain U exited and does not free= the Virtio device. | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Implication | Virtio device not freed after applica= tion 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 drive= r +------------------------------------------------------------------------= - + ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Title | Virtio incorrect header length used i= f MSI-X is disabled by kernel driver or | +| | if VIRTIO_NET_F_MAC is not negotiated= . | +| | = | ++=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ +| Reference # | IXA00384256 = | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Description | The Virtio header for host-guest comm= unication is of variable length and | +| | is dependent on whether MSI-X has bee= n enabled by the kernel driver for the network | +| | device. = | +| | = | +| | The base header length of 20 bytes wi= ll 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 thi= s bit field is not part of the Virtio | +| | specification and resolves to the VIR= TIO_NET_F_MAC feature instead. | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Implication | The DPDK kernel driver will enable MS= I-X by default, | +| | however if loaded with "intr_mode=3Dl= egacy" on a guest with a Virtio Network Device, | +| | a KVM-Qemu guest may crash with the f= ollowing error: "virtio-net header not in first | +| | element". = | +| | = | +| | If VIRTIO_NET_F_MAC feature has not b= een negotiated, then the Userspace Poll Mode | +| | Driver will assume that MSI-X has bee= n 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 disabl= ed 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 ap= plication executions with 2MB pages | +| | = | ++=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ +| Reference # | IXA00372346 = | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Description | The performance of an DPDK applicatio= n may vary across executions of an | +| | application due to a varying number o= f TLB misses depending on the location of | +| | accessed structures in memory. = | +| | This situation occurs on rare occasio= ns. | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Implication | Occasionally, relatively poor perform= ance of DPDK applications is encountered. | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Resolution/ Workaround | Using 1 GB pages results in lower usa= ge 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 M= SI interrupts | +| | = | ++=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ +| Reference # | IXA00378191 = | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Description | MSI interrupts are not supported by t= he PMD. | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| Implication | Link status change will only work wit= h 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 te= sted. | +| | = | ++--------------------------------+--------------------------------------= ------------------------------------------------+ +| 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 ------------------------------------------------------------------------= ------------ =20 --=20 2.1.0