* [dpdk-dev] [PATCH v3 1/8] doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 0/8] doc: patch set to update release notes Siobhan Butler
@ 2014-12-16 14:48 ` Siobhan Butler
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 2/8] doc: added new features to release notes Siobhan Butler
` (8 subsequent siblings)
9 siblings, 0 replies; 49+ messages in thread
From: Siobhan Butler @ 2014-12-16 14:48 UTC (permalink / raw)
To: dev
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/new_features.rst | 17 -----------------
doc/guides/rel_notes/supported_features.rst | 22 ++++++++++++++++++++++
2 files changed, 22 insertions(+), 17 deletions(-)
diff --git a/doc/guides/rel_notes/new_features.rst b/doc/guides/rel_notes/new_features.rst
index 568d0c9..a93aa3c 100644
--- a/doc/guides/rel_notes/new_features.rst
+++ b/doc/guides/rel_notes/new_features.rst
@@ -31,22 +31,5 @@
New Features
============
-* Packet Distributor library for dynamic, single-packet at a time, load balancing
-
-* IP fragmentation and reassembly library
-
-* Support for IPv6 in IP fragmentation and reassembly sample applications
-
-* Support for VFIO for mapping BARs and setting up interrupts
-
-* Link Bonding PMD Library supporting round-robin, active backup, balance(layer 2, layer 2+3, and layer 3+4) and broadcast bonding modes
-
-* Support zero copy mode RX/TX in user space vhost sample
-
-* Support multiple queues in virtio-net PMD
-
-* Support for Intel® 40GbE Controllers
-
-* Support NIC filters in addition to flow director for Intel® 1GbE and 10GbE Controllers
For further features supported in this release, see Chapter 3 Supported Features.
diff --git a/doc/guides/rel_notes/supported_features.rst b/doc/guides/rel_notes/supported_features.rst
index c51eb26..7efeff3 100644
--- a/doc/guides/rel_notes/supported_features.rst
+++ b/doc/guides/rel_notes/supported_features.rst
@@ -31,6 +31,28 @@
Supported Features
==================
+* Packet Distributor library for dynamic, single-packet at a time, load balancing
+
+* IP fragmentation and reassembly library
+
+* Support for IPv6 in IP fragmentation and reassembly sample applications
+
+* Support for VFIO for mapping BARs and setting up interrupts
+
+* Link Bonding PMD Library supporting round-robin, active backup, balance(layer 2, layer 2+3, and layer 3+4) and broadcast bonding modes
+
+* Support zero copy mode RX/TX in user space vhost sample
+
+* Support multiple queues in virtio-net PMD
+
+* Support for Intel 40GbE Controllers:
+
+ * Intel(R) XL710 40 Gigabit Ethernet Controller
+
+ * Intel(R) X710 40 Gigabit Ethernet Controller
+
+* Support NIC filters in addition to flow director for Intel� 1GbE and 10GbE Controllers
+
* Virtualization (KVM)
* Userspace vhost switch:
--
1.8.5.3
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v3 2/8] doc: added new features to release notes
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 0/8] doc: patch set to update release notes Siobhan Butler
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 1/8] doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes Siobhan Butler
@ 2014-12-16 14:48 ` Siobhan Butler
2014-12-16 14:48 ` [dpdk-dev] [PATCH 3/8] doc: added to known issue 6.10 and removed fixed issue 6.29 from rel_notes Siobhan Butler
` (7 subsequent siblings)
9 siblings, 0 replies; 49+ messages in thread
From: Siobhan Butler @ 2014-12-16 14:48 UTC (permalink / raw)
To: dev
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/new_features.rst | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/doc/guides/rel_notes/new_features.rst b/doc/guides/rel_notes/new_features.rst
index a93aa3c..00895ce 100644
--- a/doc/guides/rel_notes/new_features.rst
+++ b/doc/guides/rel_notes/new_features.rst
@@ -30,6 +30,30 @@
New Features
============
+* Link Bonding
+ * Support for 802.3ad link aggregation (mode 4) and transmit load balancing (mode 5) to the link bonding library.
+
+ * Support for registration of link status change callbacks with link bonding devices.
+
+ * Support for slaves devices which do not support link status change interrupts in the link bonding library via a link status polling mechanism.
+
+* Poll Mode Driver - 40 GbE Controllers (librte_pmd_i40e)
+
+ * Support for Flow Director
+
+ * Support for ethertype filter
+
+ * Support RSS in VF
+
+ * Support configuring redirection table with different size from 1GbE and 10 GbE
+
+ - 128/512 entries of 40GbE PF
+
+ - 64 entries of 40GbE VF
+
+ * Support configuring hash functions
+
+* Packet Distributor Sample Application
For further features supported in this release, see Chapter 3 Supported Features.
--
1.8.5.3
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH 3/8] doc: added to known issue 6.10 and removed fixed issue 6.29 from rel_notes
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 0/8] doc: patch set to update release notes Siobhan Butler
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 1/8] doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes Siobhan Butler
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 2/8] doc: added new features to release notes Siobhan Butler
@ 2014-12-16 14:48 ` Siobhan Butler
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 4/8] doc: moved known issue 6.29 to resolved issues in rel notes Siobhan Butler
` (6 subsequent siblings)
9 siblings, 0 replies; 49+ messages in thread
From: Siobhan Butler @ 2014-12-16 14:48 UTC (permalink / raw)
To: dev
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/known_issues.rst | 38 +++++++----------------------------
1 file changed, 7 insertions(+), 31 deletions(-)
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 8ef654a..1f45834 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -338,6 +338,12 @@ Not all variants of supported NIC types have been used in testing
| | |
| | The NIC device identifiers used during testing: |
| | |
+| | * Intel(R) Ethernet Controller XL710 for 40GbE QSFP+ [8086:1584] |
+| | |
+| | * Intel(R) Ethernet Controller XL710 for 40GbE QSFP+ [8086:1583] |
+| | |
+| | * Intel(R) Ethernet Controller X710 for 10GbE SFP+ [8086:1572] |
+| | |
| | * Intel® 82576 Gigabit Ethernet Controller [8086:10c9] |
| | |
| | * Intel® 82576 Quad Copper Gigabit Ethernet Controller [8086:10e8] |
@@ -940,37 +946,7 @@ Ethertype filter could receive other packets (non-assigned) in Niantic
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-Double VLAN does not work on Intel® 40G ethernet controller
------------------------------------------------------------
-
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Title | Double VLAN does not work on Intel® 40G ethernet controller |
-| | |
-+================================+======================================================================================+
-| Reference # | IXA00386480 |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | On Intel® 40G Ethernet Controller: |
-| | |
-| | Double VLAN does not work. This was confirmed a firmware issue which will be fixed |
-| | in later versions of firmware. |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | After setting double vlan to be enabled on a port, no packets can be transmitted out |
-| | on that port. |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Resolution/ Workaround | None |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Affected Environment/ Platform | All |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Driver/Module | Poll Mode Driver (PMD) |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-
-Cannot set link speed on Intel® 40G ethernet controller
+Cannot set link speed on Intel® 40GbE ethernet controller
-------------------------------------------------------
+--------------------------------+--------------------------------------------------------------------------------------+
--
1.8.5.3
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v3 4/8] doc: moved known issue 6.29 to resolved issues in rel notes
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 0/8] doc: patch set to update release notes Siobhan Butler
` (2 preceding siblings ...)
2014-12-16 14:48 ` [dpdk-dev] [PATCH 3/8] doc: added to known issue 6.10 and removed fixed issue 6.29 from rel_notes Siobhan Butler
@ 2014-12-16 14:48 ` Siobhan Butler
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 5/8] doc: remove appendix a from release notes Siobhan Butler
` (5 subsequent siblings)
9 siblings, 0 replies; 49+ messages in thread
From: Siobhan Butler @ 2014-12-16 14:48 UTC (permalink / raw)
To: dev
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/resolved_issues.rst | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/doc/guides/rel_notes/resolved_issues.rst b/doc/guides/rel_notes/resolved_issues.rst
index f9ddb7f..5e88005 100644
--- a/doc/guides/rel_notes/resolved_issues.rst
+++ b/doc/guides/rel_notes/resolved_issues.rst
@@ -1192,3 +1192,33 @@ Packet reception issues when virtualization is enabled
| Driver/Module | Poll mode drivers |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
+
+
+
+Double VLAN does not work on Intel� 40GbE ethernet contoller
+------------------------------------------------------------
+
++---------------------------------+---------------------------------------------------------------------------------------+
+| Title | Double VLAN does not work on Intel� 40GbE ethernet controller |
+| | |
++=================================+=======================================================================================+
+| Reference # | IXA00369908 |
+| | |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Description | On Intel(R) 40 GbE ethernet controller double VLAN does not work. |
+| | This was confirmed as a Firmware issue which will be fixed in later versions of |
+| | firmware. |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Implication | After setting double vlan to be enabled on a port, no packets can be transmitted out |
+| | on that port. |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Resolution/Workaround | Resolved in latest release with firmware upgrade. |
+| | |
+| | |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Affected Environment/Platform | All |
+| | |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Driver/Module | Poll mode drivers |
+| | |
++---------------------------------+---------------------------------------------------------------------------------------+
--
1.8.5.3
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v3 5/8] doc: remove appendix a from release notes
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 0/8] doc: patch set to update release notes Siobhan Butler
` (3 preceding siblings ...)
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 4/8] doc: moved known issue 6.29 to resolved issues in rel notes Siobhan Butler
@ 2014-12-16 14:48 ` Siobhan Butler
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 6/8] doc: removed reference to Intel DPDK in Rel Notes Siobhan Butler
` (4 subsequent siblings)
9 siblings, 0 replies; 49+ messages in thread
From: Siobhan Butler @ 2014-12-16 14:48 UTC (permalink / raw)
To: dev
Removing Appendix A from Release Notes as Intel Licensing information is
no longer relevant in this document.
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/appendices.rst | 324 ------------------------------------
doc/guides/rel_notes/index.rst | 44 -----
2 files changed, 368 deletions(-)
delete mode 100644 doc/guides/rel_notes/appendices.rst
diff --git a/doc/guides/rel_notes/appendices.rst b/doc/guides/rel_notes/appendices.rst
deleted file mode 100644
index 6dec2e1..0000000
--- a/doc/guides/rel_notes/appendices.rst
+++ /dev/null
@@ -1,324 +0,0 @@
-.. BSD LICENSE
- Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
- All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
-
- * Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
- * Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in
- the documentation and/or other materials provided with the
- distribution.
- * Neither the name of Intel Corporation nor the names of its
- contributors may be used to endorse or promote products derived
- from this software without specific prior written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-Appendix A Intel® DPDK License Overview
-=========================================
-
-
-The following describes the various licenses used by the Intel® Data Plane Development Kit (Intel® DPDK).
-The purpose of the Intel® DPDK is to prove the abilities of the Intel® architecture processors and to provide users with a strong set of examples, libraries and proof points.
-By placing the majority of this software under the BSD License, users may choose to use the Intel® as is, parts of it, or just the ideas for their programs.
-All code may be modified by the user to suit their project needs and requirements.
-
-.. note::
-
- The license in each source file takes precedence over this document, and should be used as the definitive license for that file.
- All users should seek their legal team's guidance with respect to the licensing used by the Intel® DPDK.
-
-
-
-The following table lists those files (or libraries) that are not under a BSD License. In some cases, these files are part of the standard Intel® DPDK release package,
-and in other cases may be a separate package that requires a separate download to be added to the Intel® DPDK. This document spells out those cases where possible.
-
-The sections following the table provide the various licenses used. Please note that copyright notices may change overtime.
-It is the responsibility of all users to understand these licenses and seek their legal team's guidance.
-
-The use of the GPLv2 License is confined to files in kernel loadable modules.
-
-The use of the Dual BSD/LGPLv2 License and Dual BSD/GPL License allows use with either free/open source software or with proprietary software in userspace.
-
-
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| File | Description | License |
-| | | |
-+===================================================+======================================================================================================================+======================================+
-| igb_uio.c | **1st Released** | GPLv2 License Information |
-| | : 1.0 | |
-| | | |
-| | **Location** | |
-| | : | |
-| | DPDK/lib/librte_eal/linuxapp/igb_uio/ | |
-| | | |
-| | **Description** | |
-| | : This file is used for a kernel loadable module which is responsible for unbinding NICs from the Linux kernel | |
-| | and binding them to the Intel® DPDK | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| kni_dev.h kni_ethtool.c kni_misc.c kni_net.c | **1st Released** | GPLv2 License Information |
-| | : 1.3 | |
-| | | |
-| | **Location** | |
-| | : DPDK/lib/librte_eal/linuxapp/kni/ | |
-| | | |
-| | **Description** | |
-| | : The KNI kernel loadable module is a standard net driver which allows Intel DPDK Linux userspace applications | |
-| | to exchange packets/data with the Linux kernel. | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| rte_kni_common.h | **1st Released** | Dual BSD/LGPLv2 License Information |
-| | : 1.3 | |
-| | | |
-| | **Location** | |
-| | : DPDK/lib/librte_eal/linuxapp/eal/include/exec-env/ | |
-| | | |
-| | **Description** | |
-| | : The KNI header files is utilized by both the Intel DPDK userspace application and the KNI kernel loadable module | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| All files under this directory are for the | **1st Released** | GPLv2 License Information |
-| ethtool functionality. | : 1.3 | |
-| | | |
-| | **Location** | |
-| | : DPDK/lib/librte_eal/linuxapp/kni/ethtool | |
-| | | |
-| | **Description** | |
-| | : The igb and ixgbe drivers for the Ethtool function available with the KNI kernel loadable. | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| rte_pci_dev_ids.h | **1st Released** | Dual BSD/GPL License Information |
-| | : 1.3 | |
-| | | |
-| | **Location** | |
-| | : DPDK/lib/librte_eal/common/include | |
-| | | |
-| | **Description** | |
-| | : Contains the PCI device ids for all devices. | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-
-Added rte_dom0_mm.h file for Dual BSD/LGPLv2 License information:
-
-rte_dom0_mm.h 1st Released 1.6.0
-
-Location: DPDK/lib/librte_eal/eal/include/exec-env/
-
-Description: The Dom0 header file is utilized by both the Intel® DPDK userspace application and the Dom0 kernel loadable module
-
-Added dom0_mm_misc.h and dom0_mm_misc.c file for Dual BSD/GPLv2 License Information:
-
-dom0_mm_dev.h 1st Released 1.6.0
-
-dom0_mm_dev.c Location: DPDK/lib/librte_eal/linuxapp/xen_dom0
-
-Description: The Dom0 memory management kernel loadable module is a misc device driver which is used to facilitate allocating and mapping via an **IOCTL** (allocation) and **MMAP** (mapping).
-
-
-A.1 BSD License
----------------
-
-.. code-block:: c
-
- /*-
- * BSD LICENSE
- *
- * Copyright(c) 2010-2012 Intel Corporation. All rights reserved.
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * * Redistributions of source code must retain the above copyright
- * notice, this list of conditions and the following disclaimer.
- * * Redistributions in binary form must reproduce the above copyright
- * notice, this list of conditions and the following disclaimer in
- * the documentation and/or other materials provided with the
- * distribution.
- * * Neither the name of Intel Corporation nor the names of its
- * contributors may be used to endorse or promote products derived
- * from this software without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- *
- */
-
-A.2 GPLv2 License Information
------------------------------
-
-.. code-block:: c
-
- /*-
- *
- * Copyright (c) 2010-2012, Intel Corporation
- *
- * This program is free software; you can redistribute it and/or
- * modify it under the terms of the GNU General Public License
- * as published by the Free Software Foundation; either version 2
- * of the License, or (at your option) any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
- *
-..
-
- \* GNU GPL V2: `http://www.gnu.org/licenses/old-licenses/gpl-2.0.html <http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>`_
-
-.. code-block:: c
-
- *
- */
-
-A.3 Dual BSD/LGPLv2 License Information
----------------------------------------
-
-.. code-block:: c
-
- /*
- This file is provided under a dual BSD/LGPLv2 license. When using
- or redistributing this file, you may do so under either license.
-
- GNU LESSER GENERAL PUBLIC LICENSE
-
- Copyright(c) 2007,2008,2009 Intel Corporation. All rights reserved.
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of version 2.1 of the GNU Lesser General Public License
- as published by the Free Software Foundation.
-
- This program is distributed in the hope that it will be useful, but WITHOUT ANY
- WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- PARTICULAR PURPOSE. See the GNU
- Lesser General Public License for more details.
-
- You should have received a copy of the GNU Lesser General Public License along with
- this program; if not, write to the Free Software
- Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
-
-
- Contact Information: Intel Corporation
-
- BSD LICENSE
-
- Copyright(c) 2010-2012 Intel Corporation.All rights reserved. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without modification, are
- permitted provided that the following conditions are met:
-
- Redistributions of source code must retain the above copyright notice, this list of
- conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list
- of conditions and the following disclaimer in the documentation and/or other
- materials provided with the distribution.
- Neither the name of Intel Corporation nor the names of its contributors may be used
- to endorse or promote products derived from this software without specific prior
- written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
- EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
- SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
- TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
- BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
- CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
- ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
- DAMAGE.
- */
-
-
-A.4 Dual BSD/GPL License Information
-------------------------------------
-
-.. code-block:: c
-
- /*-
- * This file is provided under a dual BSD/GPLv2 license. When using or
- * redistributing this file, you may do so under either license.
- *
- * GPL LICENSE SUMMARY
- *
- * Copyright(c) 2010-2012 Intel Corporation. All rights reserved.
- *
- * This program is free software; you can redistribute it and/or modify
- * it under the terms of version 2 of the GNU General Public License as
- * published by the Free Software Foundation.
- *
- * This program is distributed in the hope that it will be useful, but
- * WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
- * General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
- * The full GNU General Public License is included in this distribution
- * in the file called LICENSE.GPL.
- *
- * Contact Information:
- * Intel Corporation
- *
- * BSD LICENSE
- *
- * Copyright(c) 2010-2012 Intel Corporation. All rights reserved.
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * * Redistributions of source code must retain the above copyright
- * notice, this list of conditions and the following disclaimer.
- * * Redistributions in binary form must reproduce the above copyright
- * notice, this list of conditions and the following disclaimer in
- * the documentation and/or other materials provided with the
- * distribution.
- * * Neither the name of Intel Corporation nor the names of its
- * contributors may be used to endorse or promote products derived
- * from this software without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- *
- */
diff --git a/doc/guides/rel_notes/index.rst b/doc/guides/rel_notes/index.rst
index e9a3d21..69e59d4 100644
--- a/doc/guides/rel_notes/index.rst
+++ b/doc/guides/rel_notes/index.rst
@@ -35,49 +35,6 @@ Package Version: 1.7
|today|
-INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS.
-NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT.
-EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY,
-RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT,
-COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
-
-A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death.
-SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES,
-AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY,
-ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN,
-MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS.
-
-Intel may make changes to specifications and product descriptions at any time, without notice.
-Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined".
-Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.
-The information here is subject to change without notice.
-Do not finalize a design with this information.
-
-The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications.
-Current characterized errata are available on request.
-
-Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
-
-Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling
-1-800-548-4725, or go to:
-`http://www.intel.com/design/literature.htm <http://www.intel.com/design/literature.htm>`_
-
-Any software source code reprinted in this document is furnished for informational purposes only and may only be used or copied and no license, express or implied, by estoppel or otherwise,
-to any of the reprinted source code is granted by this document.
-
-Code Names are only for use by Intel to identify products, platforms, programs, services, etc. ("products") in development by
-Intel that have not been made commercially available to the public, i.e., announced, launched or shipped. They are never to be used as "commercial" names for products.
-Also, they are not intended to function as trademarks.
-
-See Appendix A for an overview of the applicable software licenses.
-
-Intel, the Intel logo, Intel Core and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
-
-\*Other names and brands may be claimed as the property of others.
-
-Copyright © 2012-2014 , Intel Corporation. All rights reserved.
-
-
Contents
.. toctree::
@@ -92,4 +49,3 @@ Contents
known_issues
resolved_issues
faq
- appendices
--
1.8.5.3
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v3 6/8] doc: removed reference to Intel DPDK in Rel Notes
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 0/8] doc: patch set to update release notes Siobhan Butler
` (4 preceding siblings ...)
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 5/8] doc: remove appendix a from release notes Siobhan Butler
@ 2014-12-16 14:48 ` Siobhan Butler
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 7/8] doc: updated resolved issues with old known issues Siobhan Butler
` (3 subsequent siblings)
9 siblings, 0 replies; 49+ messages in thread
From: Siobhan Butler @ 2014-12-16 14:48 UTC (permalink / raw)
To: dev
Removed multiple references to Intel(R) DPDK where no longer
relevant.
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/faq.rst | 14 +++---
doc/guides/rel_notes/known_issues.rst | 38 +++++++--------
doc/guides/rel_notes/rel_description.rst | 36 ++++++---------
doc/guides/rel_notes/resolved_issues.rst | 72 ++++++++++++++---------------
doc/guides/rel_notes/supported_features.rst | 10 ++--
doc/guides/rel_notes/supported_os.rst | 2 +-
doc/guides/rel_notes/updating_apps.rst | 12 +++--
7 files changed, 90 insertions(+), 94 deletions(-)
diff --git a/doc/guides/rel_notes/faq.rst b/doc/guides/rel_notes/faq.rst
index dfc34e6..054db10 100644
--- a/doc/guides/rel_notes/faq.rst
+++ b/doc/guides/rel_notes/faq.rst
@@ -36,7 +36,7 @@ When running the test application, I get “EAL: map_all_hugepages(): open faile
This is most likely due to the test application not being run with sudo to promote the user to a superuser.
Alternatively, applications can also be run as regular user.
-For more information, please refer to *Intel® DPDK Getting Started Guide*.
+For more information, please refer to *DPDK Getting Started Guide*.
If I want to change the number of TLB Hugepages allocated, how do I remove the original pages allocated?
--------------------------------------------------------------------------------------------------------
@@ -49,7 +49,7 @@ If you look in the directory, you will see n number of 2M pages files. If you sp
These are then placed in memory segments to get contiguous memory.
If you need to change the number of pages, it is easier to first remove the pages. The tools/setup.sh script provides an option to do this.
-See the “Quick Start Setup Script” section in the *Intel® DPDK Getting Started Guide* for more information.
+See the “Quick Start Setup Script” section in the *DPDK Getting Started Guide* for more information.
If I execute “l2fwd -c f -m 64 –n 3 -- -p 3”, I get the following output, indicating that there are no socket 0 hugepages to allocate the mbuf and ring structures to?
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -59,14 +59,14 @@ I have set up a total of 1024 Hugepages (that is, allocated 512 2M pages to each
The -m command line parameter does not guarantee that huge pages will be reserved on specific sockets. Therefore, allocated huge pages may not be on socket 0.
To request memory to be reserved on a specific socket, please use the --socket-mem command-line parameter instead of -m.
-I am running a 32-bit Intel® DPDK application on a NUMA system, and sometimes the application initializes fine but cannot allocate memory. Why is that happening?
+I am running a 32-bit DPDK application on a NUMA system, and sometimes the application initializes fine but cannot allocate memory. Why is that happening?
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
32-bit applications have limitations in terms of how much virtual memory is available, hence the number of hugepages they are able to allocate is also limited (1 GB per page size).
If your system has a lot (>1 GB per page size) of hugepage memory, not all of it will be allocated.
Due to hugepages typically being allocated on a local NUMA node, the hugepages allocation the application gets during the initialization depends on which
NUMA node it is running on (the EAL does not affinitize cores until much later in the initialization process).
-Sometimes, the Linux OS runs the Intel® DPDK application on a core that is located on a different NUMA node from Intel® DPDK master core and
+Sometimes, the Linux OS runs the DPDK application on a core that is located on a different NUMA node from DPDK master core and
therefore all the hugepages are allocated on the wrong socket.
To avoid this scenario, either lower the amount of hugepage memory available to 1 GB per page size (or less), or run the application with taskset
@@ -102,7 +102,7 @@ Traditionally, there is a trade-off between throughput and latency. An applicati
but the end-to-end latency of an average packet typically increases as a result.
Similarly, the application can be tuned to have, on average, a low end-to-end latency at the cost of lower throughput.
-To achieve higher throughput, the Intel® DPDK attempts to aggregate the cost of processing each packet individually by processing packets in bursts.
+To achieve higher throughput, the DPDK attempts to aggregate the cost of processing each packet individually by processing packets in bursts.
Using the testpmd application as an example, the “burst” size can be set on the command line to a value of 16 (also the default value).
This allows the application to request 16 packets at a time from the PMD.
The testpmd application then immediately attempts to transmit all the packets that were received, in this case, all 16 packets.
@@ -144,11 +144,11 @@ For best performance with NUMA disabled, only one socket should be populated.
I am getting errors about not being able to open files. Why?
------------------------------------------------------------
-As the Intel® DPDK operates, it opens a lot of files, which can result in reaching the open files limits, which is set using the ulimit command or in the limits.conf file.
+As the DPDK operates, it opens a lot of files, which can result in reaching the open files limits, which is set using the ulimit command or in the limits.conf file.
This is especially true when using a large number (>512) of 2 MB huge pages. Please increase the open file limit if your application is not able to open files.
This can be done either by issuing a ulimit command or editing the limits.conf file. Please consult Linux* manpages for usage information.
-Does my kernel require patching to run the Intel® DPDK?
+Does my kernel require patching to run the DPDK?
-------------------------------------------------------
Any kernel greater than version 2.6.33 can be used without any patches applied. The following kernels may require patches to provide hugepage support:
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 1f45834..4979e66 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -31,7 +31,7 @@
Known Issues and Limitations
============================
-This section describes known issues with the Intel® DPDK software, Release 1.6.0.
+This section describes known issues with the DPDK software, Release 1.8.0.
Pause Frame Forwarding does not work properly on igb
----------------------------------------------------
@@ -112,13 +112,13 @@ Vhost-xen cannot detect Domain U application exit on Xen version 4.0.1
| Reference # | IXA00168947 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | When using Intel® DPDK applications on Xen 4.0.1, e.g. TestPMD Sample Application, |
+| 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 |
+| | 4.0.1 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Resolution | |
@@ -154,7 +154,7 @@ Virtio incorrect header length used if MSI-X is disabled by kernel driver
| | specification and resolves to the VIRTIO_NET_F_MAC feature instead. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | The Intel® DPDK kernel driver will enable MSI-X by default, |
+| 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”. |
@@ -338,11 +338,11 @@ Not all variants of supported NIC types have been used in testing
| | |
| | The NIC device identifiers used during testing: |
| | |
-| | * Intel(R) Ethernet Controller XL710 for 40GbE QSFP+ [8086:1584] |
+| | * Intel(R) Ethernet Controller XL710 for 40GbE QSFP+ [8086:1584] |
| | |
-| | * Intel(R) Ethernet Controller XL710 for 40GbE QSFP+ [8086:1583] |
+| | * Intel(R) Ethernet Controller XL710 for 40GbE QSFP+ [8086:1583] |
| | |
-| | * Intel(R) Ethernet Controller X710 for 10GbE SFP+ [8086:1572] |
+| | * Intel(R) Ethernet Controller X710 for 10GbE SFP+ [8086:1572] |
| | |
| | * Intel® 82576 Gigabit Ethernet Controller [8086:10c9] |
| | |
@@ -425,13 +425,13 @@ Unstable system performance across application executions with 2MB pages
| Reference # | IXA00372346 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | The performance of an Intel® DPDK application may vary across executions of an |
+| 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 Intel® DPDK applications is encountered.|
+| 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. |
@@ -536,7 +536,7 @@ PMD does not work with --no-huge EAL command line parameter
| Reference # | IXA00373461 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | Currently, the Intel® DPDK does not store any information about memory allocated by |
+| Description | Currently, the DPDK does not store any information about memory allocated by |
| | malloc() (for example, NUMA node, physical address), hence PMD drivers do not work |
| | when the --no-huge command line parameter is supplied to EAL. |
| | |
@@ -547,7 +547,7 @@ PMD does not work with --no-huge EAL command line parameter
| Resolution/ Workaround | Use huge page memory or use VFIO to map devices. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Affected Environment/ Platform | Systems running the Intel® DPDK on Linux |
+| Affected Environment/ Platform | Systems running the DPDK on Linux |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Driver/Module | Poll Mode Driver (PMD) |
@@ -701,24 +701,24 @@ Discrepancies between statistics reported by different NICs
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-Error reported opening files on Intel® DPDK initialization
-----------------------------------------------------------
+Error reported opening files on DPDK initialization
+---------------------------------------------------
+--------------------------------+--------------------------------------------------------------------------------------+
-| Title | Error reported opening files on Intel® DPDK initialization |
+| Title | Error reported opening files on DPDK initialization |
| | |
+================================+======================================================================================+
| Reference # | 91 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | On Intel® DPDK application startup, errors may be reported when opening files as |
+| Description | On DPDK application startup, errors may be reported when opening files as |
| | part of the initialization process. This occurs if a large number, for example, 500 |
| | or more, or if hugepages are used, due to the per-process limit on the number of |
| | open files. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | The Intel® DPDK application may fail to run. |
+| Implication | The DPDK application may fail to run. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Resolution/ Workaround | If using 2 MB hugepages, consider switching to a fewer number of 1 GB pages. |
@@ -890,11 +890,11 @@ GCC might generate Intel® AVX instructions forprocessors without Intel® AVX su
| Reference # | IXA00382439 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | When compiling Intel® DPDK (and any Intel® DPDK app), gcc may generate Intel® AVX |
+| Description | When compiling Intel® DPDK (and any DPDK app), gcc may generate Intel® AVX |
| | instructions, even when the processor does not support Intel® AVX. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | Any Intel® DPDK app might crash while starting up. |
+| Implication | Any DPDK app might crash while starting up. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Resolution/ Workaround | Either compile using icc or set EXTRA_CFLAGS=’-O3’ prior to compilation. |
@@ -947,7 +947,7 @@ Ethertype filter could receive other packets (non-assigned) in Niantic
+--------------------------------+--------------------------------------------------------------------------------------+
Cannot set link speed on Intel® 40GbE ethernet controller
--------------------------------------------------------
+---------------------------------------------------------
+--------------------------------+--------------------------------------------------------------------------------------+
| Title | Cannot set link speed on Intel® 40G ethernet controller |
diff --git a/doc/guides/rel_notes/rel_description.rst b/doc/guides/rel_notes/rel_description.rst
index d159b3c..8da53c4 100644
--- a/doc/guides/rel_notes/rel_description.rst
+++ b/doc/guides/rel_notes/rel_description.rst
@@ -32,22 +32,14 @@ Description of Release
======================
These release notes cover the new features,
-fixed bugs and known issues for Intel® Data Plane Development Kit (Intel® DPDK) release version 1.7.0.
+fixed bugs and known issues for Data Plane Development Kit (DPDK) release version 1.7.0.
-For instructions on compiling and running the release, see the *Intel® DPDK Getting Started Guide*.
+For instructions on compiling and running the release, see the *DPDK Getting Started Guide*.
-Important Note
---------------
+Using DPDK Upgrade Patches
+--------------------------
-All Intel® DPDK questions and technical problems including those regarding the Ethernet* Controllers for the Poll Mode Driver should be reported through the Intel® Premier Support site
-`http://premier.intel.com/premier <http://premier.intel.com/premier>`_
-or access your IBL account and click the **Intel® Premier Support** link to enter issues under the Product Name “Data Plane Development Kit (DPDK)”,
-which are then routed to our support team.
-
-Using Intel® DPDK Upgrade Patches
----------------------------------
-
-For minor updates to the main Intel® DPDK releases, the software may be made available both as a new full package and as a patch file to be applied to the previously released package.
+For minor updates to the main DPDK releases, the software may be made available both as a new full package and as a patch file to be applied to the previously released package.
In the latter case, the following commands should be used to apply the patch on top of the already-installed package for the previous release:
.. code-block:: console
@@ -55,7 +47,7 @@ In the latter case, the following commands should be used to apply the patch on
# cd $RTE_SDK
# patch –p1 < /path/to/patch/file
-Once the patch has been applied cleanly, the Intel® DPDK can be recompiled and used as before (described in the *Intel® DPDK Getting Started Guide*).
+Once the patch has been applied cleanly, the DPDK can be recompiled and used as before (described in the *DPDK Getting Started Guide*).
.. note::
@@ -65,25 +57,25 @@ Once the patch has been applied cleanly, the Intel® DPDK can be recompiled and
Documentation Roadmap
---------------------
-The following is a list of Intel® DPDK documents in the suggested reading order:
+The following is a list of DPDK documents in the suggested reading order:
* **Release Notes**
(this document): Provides release-specific information, including supported features, limitations, fixed issues, known issues and so on.
Also, provides the answers to frequently asked questions in FAQ format.
* **Getting Started Guide**
- : Describes how to install and configure the Intel® DPDK software; designed to get users up and running quickly with the software.
+ : Describes how to install and configure the DPDK software; designed to get users up and running quickly with the software.
* **FreeBSD* Getting Started Guide**
- : A document describing the use of the Intel® DPDK with FreeBSD* has been added in Intel® DPDK Release 1.6.0.
- Refer to this guide for installation and configuration instructions to get started using the Intel® DPDK with FreeBSD*.
+ : A document describing the use of the DPDK with FreeBSD* has been added in DPDK Release 1.6.0.
+ Refer to this guide for installation and configuration instructions to get started using the DPDK with FreeBSD*.
* **Programmer's Guide**
: Describes:
* The software architecture and how to use it (through examples), specifically in a Linux* application (linuxapp) environment
- * The content of the Intel® DPDK, the build system (including the commands that can be used in the root Intel® DPDK Makefile to build the development kit and an application)
+ * The content of the DPDK, the build system (including the commands that can be used in the root DPDK Makefile to build the development kit and an application)
and guidelines for porting an application
* Optimizations used in the software and those that should be considered for new development
@@ -91,7 +83,7 @@ The following is a list of Intel® DPDK documents in the suggested reading order
A glossary of terms is also provided.
* **API Reference**
- : Provides detailed information about Intel® DPDK functions, data structures and other programming constructs.
+ : Provides detailed information about DPDK functions, data structures and other programming constructs.
* **Sample Applications User Guide**
: Describes a set of sample applications. Each chapter describes a sample application that showcases specific functionality and provides instructions on how to compile,
@@ -160,11 +152,11 @@ The following is a list of Intel® DPDK documents in the suggested reading order
Once the libraries are created, they can be found in the build/app directory.
- * The test application provides a variety of specific tests for the various functions in the Intel® DPDK.
+ * The test application provides a variety of specific tests for the various functions in the DPDK.
* The testpmd application provides a number of different packet throughput tests and examples of features such as
how to use the Flow Director found in the Intel® 82599 10 Gigabit Ethernet Controller.
- The testpmd application is documented in the *Intel® DPDK Testpmd Application Note* (525362).
+ The testpmd application is documented in the *DPDK Testpmd Application Note* (525362).
The test application is not currently documented.
However, you should be able to run and use test application with the command line help that is provided in the application.
diff --git a/doc/guides/rel_notes/resolved_issues.rst b/doc/guides/rel_notes/resolved_issues.rst
index 5e88005..f47924c 100644
--- a/doc/guides/rel_notes/resolved_issues.rst
+++ b/doc/guides/rel_notes/resolved_issues.rst
@@ -200,7 +200,7 @@ Device initialization failure with Intel® Ethernet Server Adapter X520-T2
| Reference # | 55 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Description | If this device is bound to the Linux kernel IXGBE driver when the Intel® DPDK is |
+| Description | If this device is bound to the Linux kernel IXGBE driver when the DPDK is |
| | initialized, DPDK is initialized, the device initialization fails with error code -17 |
| | “IXGBE_ERR_PHY_ADDR_INVALID”. |
| | |
@@ -208,7 +208,7 @@ Device initialization failure with Intel® Ethernet Server Adapter X520-T2
| Implication | The device is not initialized and cannot be used by an application. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution/Workaround | Introduced a small delay in device initialization to allow Intel® DPDK to always find |
+| Resolution/Workaround | Introduced a small delay in device initialization to allow DPDK to always find |
| | the device. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -219,11 +219,11 @@ Device initialization failure with Intel® Ethernet Server Adapter X520-T2
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-Intel® DPDK kernel module is incompatible with Linux kernel version 3.3
------------------------------------------------------------------------
+DPDK kernel module is incompatible with Linux kernel version 3.3
+----------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
-| Title | Intel® DPDK kernel module is incompatible with Linux kernel version 3.3 |
+| Title | DPDK kernel module is incompatible with Linux kernel version 3.3 |
| | |
+=================================+=======================================================================================+
| Reference # | IXA00373232 |
@@ -430,7 +430,7 @@ Port not found issue with Intel® 82580 Gigabit Ethernet Controller
+---------------------------------+---------------------------------------------------------------------------------------+
| Description | After going through multiple driver unbind/bind cycles, an Intel® 82580 |
| | Ethernet Controller port may no longer be found and initialized by the |
-| | Intel® DPDK. |
+| | DPDK. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Implication | The port will be unusable. |
@@ -506,8 +506,8 @@ Promiscuous mode for 82580 NICs can only be enabled after a call to rte_eth_dev_
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-Incorrect CPU socket information reported in /proc/cpuinfo can prevent the Intel® DPDK from running
----------------------------------------------------------------------------------------------------
+Incorrect CPU socket information reported in /proc/cpuinfo can prevent the DPDK from running
+--------------------------------------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
| Title | Incorrect CPU socket information reported in /proc/cpuinfo can prevent the Intel® |
@@ -517,14 +517,14 @@ Incorrect CPU socket information reported in /proc/cpuinfo can prevent the Intel
| Reference # | 63 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Description | The Intel® DPDK users information supplied by the Linux kernel to determine the |
+| Description | The DPDK users information supplied by the Linux kernel to determine the |
| | hardware properties of the system being used. On rare occasions, information supplied |
| | by /proc/cpuinfo does not match that reported elsewhere. In some cases, it has been |
| | observed that the CPU socket numbering given in /proc/cpuinfo is incorrect and this |
-| | can prevent Intel® DPDK from operating. |
+| | can prevent DPDK from operating. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Implication | The Intel® DPDK cannot run on systems where /proc/cpuinfo does not report the correct |
+| Implication | The DPDK cannot run on systems where /proc/cpuinfo does not report the correct |
| | CPU socket topology. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -578,7 +578,7 @@ L3FWD-VF might lose CRC bytes
| Description | Currently, the CRC stripping configuration does not affect the VF driver. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Implication | Packets transmitted by the Intel® DPDK in the VM may be lacking 4 bytes (packet CRC). |
+| Implication | Packets transmitted by the DPDK in the VM may be lacking 4 bytes (packet CRC). |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Resolution/ Workaround | Set “strip_crc” to 1 in the sample applications that use the VF PMD. |
@@ -591,8 +591,8 @@ L3FWD-VF might lose CRC bytes
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-32-bit Intel® DPDK sample applications fails when using more than one 1 GB hugepage
------------------------------------------------------------------------------------
+32-bit DPDK sample applications fails when using more than one 1 GB hugepage
+----------------------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
| Title | 32-bit Intel® DPDK sample applications fails when using more than one 1 GB hugepage |
@@ -646,11 +646,11 @@ l2fwd fails to launch if the NIC is the Intel® 82571EB Gigabit Ethernet Control
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-32-bit Intel® DPDK applications may fail to initialize on 64-bit OS
--------------------------------------------------------------------
+32-bit DPDK applications may fail to initialize on 64-bit OS
+------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
-| Title | 32-bit Intel® DPDK applications may fail to initialize on 64-bit OS |
+| Title | 32-bit DPDK applications may fail to initialize on 64-bit OS |
| | |
+=================================+=======================================================================================+
| Reference # | IXA00378513 |
@@ -739,12 +739,12 @@ Config file change can cause build to fail
| Reference # | IXA00369247 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Description | If a change in a config file results in some Intel® DPDK files that were needed no |
+| Description | If a change in a config file results in some DPDK files that were needed no |
| | longer being needed, the build will fail. This is because the \*.o file will still |
| | exist, and the linker will try to link it. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Implication | Intel® DPDK compilation failure |
+| Implication | DPDK compilation failure |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Resolution | The Makefile now provides instructions to clean out old kernel module object files. |
@@ -768,8 +768,8 @@ rte_cmdline library should not be used in production code due to limited testing
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Description | The rte_cmdline library provides a command line interface for use in sample |
-| | applications and test applications distributed as part of Intel® DPDK. However, it is |
-| | not validated to the same standard as other Intel® DPDK libraries. |
+| | applications and test applications distributed as part of DPDK. However, it is |
+| | not validated to the same standard as other DPDK libraries. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Implication | It may contain bugs or errors that could cause issues in production applications. |
@@ -1017,18 +1017,18 @@ EAL can silently reserve less memory than requested
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-SSH connectivity with the board may be lost when starting an Intel® DPDK application
-------------------------------------------------------------------------------------
+SSH connectivity with the board may be lost when starting a DPDK application
+----------------------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
-| Title | SSH connectivity with the board may be lost when starting an Intel® DPDK application |
+| Title | SSH connectivity with the board may be lost when starting a DPDK application |
| | |
+=================================+=======================================================================================+
| Reference # | 26 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Description | Currently, the Intel® DPDK takes over all the NICs found on the board that are |
-| | supported by the Intel® DPDK. This results in these NICs being removed from the NIC |
+| | supported by the DPDK. This results in these NICs being removed from the NIC |
| | set handled by the kernel,which has the side effect of any SSH connection being |
| | terminated. See also issue #27. |
| | |
@@ -1036,8 +1036,8 @@ SSH connectivity with the board may be lost when starting an Intel® DPDK applic
| Implication | Loss of network connectivity to board. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution | Intel® DPDK now no longer binds ports on startup. Please refer to the Getting Started |
-| | Guide for information on how to bind/unbind ports from Intel® DPDK. |
+| Resolution | DPDK now no longer binds ports on startup. Please refer to the Getting Started |
+| | Guide for information on how to bind/unbind ports from DPDK. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Affected Environment/Platform | Systems using a Intel®DPDK supported NIC for remote system access |
@@ -1065,12 +1065,12 @@ Remote network connections lost when running autotests or sample applications
| Implication | Loss of network connectivity to board when connected remotely. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution | Intel® DPDK now no longer binds ports on startup. |
+| Resolution | DPDK now no longer binds ports on startup. |
| | Please refer to the Getting Started Guide for information on how to bind/unbind ports |
-| | from Intel® DPDK. |
+| | from DPDK. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Affected Environment/Platform | Systems using a Intel® DPDK supported NIC for remote system access |
+| Affected Environment/Platform | Systems using a DPDK supported NIC for remote system access |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Driver/Module | Sample applications |
@@ -1089,10 +1089,10 @@ KNI may not work properly in a multi-process environment
+---------------------------------+---------------------------------------------------------------------------------------+
| Description | Some of the network interface operations such as, MTU change or link UP/DOWN, when |
| | executed on KNI interface, might fail in a multi-process environment, although they |
-| | are normally successful in the Intel® DPDK single process environment. |
+| | are normally successful in the DPDK single process environment. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Implication | Some network interface operations on KNI cannot be used in an Intel® DPDK |
+| Implication | Some network interface operations on KNI cannot be used in a DPDK |
| | multi-process environment. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -1119,14 +1119,14 @@ Hash library cannot be used in multi-process applications with multiple binaries
| Description | The hash function used by a given hash-table implementation is referenced in the code |
| | by way of a function pointer. This means that it cannot work in cases where the hash |
| | function is at a different location in the code segment in different processes, as is |
-| | the case where an Intel® DPDK multi-process application uses a number of different |
+| | the case where a DPDK multi-process application uses a number of different |
| | binaries, for example, the client-server multi-process example. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Implication | The Hash library will not work if shared by multiple processes. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution/Workaround | New API was added for multiprocess scenario. Please refer to Intel® DPDK Programmer’s |
+| Resolution/Workaround | New API was added for multiprocess scenario. Please refer to DPDK Programmer’s |
| | Guide for more information. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -1182,7 +1182,7 @@ Packet reception issues when virtualization is enabled
| Implication | An application requiring packet transmission or reception will not function. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution/Workaround | Intel® DPDK Poll Mode Driver now has the ability to map correct physical addresses to |
+| Resolution/Workaround | DPDK Poll Mode Driver now has the ability to map correct physical addresses to |
| | the device structures. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -1205,7 +1205,7 @@ Double VLAN does not work on Intel� 40GbE ethernet contoller
| Reference # | IXA00369908 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Description | On Intel(R) 40 GbE ethernet controller double VLAN does not work. |
+| Description | On Intel(R) 40 GbE ethernet controller double VLAN does not work. |
| | This was confirmed as a Firmware issue which will be fixed in later versions of |
| | firmware. |
+---------------------------------+---------------------------------------------------------------------------------------+
diff --git a/doc/guides/rel_notes/supported_features.rst b/doc/guides/rel_notes/supported_features.rst
index 7efeff3..37e5416 100644
--- a/doc/guides/rel_notes/supported_features.rst
+++ b/doc/guides/rel_notes/supported_features.rst
@@ -61,7 +61,7 @@ Supported Features
* Virtualization (Xen)
- * Support for Intel® DPDK application running on Xen Domain0 without hugepages.
+ * Support for DPDK application running on Xen Domain0 without hugepages.
* Para-virtualization
@@ -70,7 +70,7 @@ Supported Features
Support userspace packet switching back-end example in host domain
* FreeBSD* 9.2 support for librte_pmd_e1000, librte_pmd_ixgbe and Virtual Function variants.
- Please refer to the *Intel® DPDK for FreeBSD\* Getting Started Guide*.
+ Please refer to the *DPDK for FreeBSD\* Getting Started Guide*.
Application support has been added for the following:
* multiprocess/symmetric_mp
@@ -87,7 +87,7 @@ Supported Features
* New VMXNET3 driver for the paravirtual device presented to a VM by the VMware* ESXi Hypervisor.
-* BETA: example support for basic Netmap applications on Intel® DPDK
+* BETA: example support for basic Netmap applications on DPDK
* Support for the wireless KASUMI algorithm in the dpdk_qat sample application
@@ -157,7 +157,7 @@ Supported Features
* Improved scalability for scheduling large numbers of timers using the rte_timer library
-* Support for building the Intel® DPDK as a shared library
+* Support for building the DPDK as a shared library
* Support for Intel® Ethernet Server Bypass Adapter X520-SR2
@@ -362,7 +362,7 @@ Supported Features
* Header files for common protocols (IP, SCTP, TCP, UDP)
-* Improved multi-process application support, allowing multiple co-operating Intel® DPDK
+* Improved multi-process application support, allowing multiple co-operating DPDK
processes to access the NIC port queues directly.
* CPU-specific compiler optimization
diff --git a/doc/guides/rel_notes/supported_os.rst b/doc/guides/rel_notes/supported_os.rst
index fb23dda..739cb2c 100644
--- a/doc/guides/rel_notes/supported_os.rst
+++ b/doc/guides/rel_notes/supported_os.rst
@@ -46,4 +46,4 @@ The following Linux* distributions were successfully used to generate or run the
* SUSE Enterprise Linux* 11 SP2
These distributions may need additional packages that are not installed by default, or a specific kernel.
-Refer to the *Intel® DPDK Getting Started Guide* for details.
+Refer to the *DPDK Getting Started Guide* for details.
diff --git a/doc/guides/rel_notes/updating_apps.rst b/doc/guides/rel_notes/updating_apps.rst
index ba8012d..034554d 100644
--- a/doc/guides/rel_notes/updating_apps.rst
+++ b/doc/guides/rel_notes/updating_apps.rst
@@ -1,11 +1,15 @@
Updating Applications from Previous Versions
============================================
-Although backward compatibility is being maintained across Intel® DPDK releases, code written for previous versions of the Intel® DPDK
-may require some code updates to benefit from performance and user experience enhancements provided in later Intel® DPDK releases.
+Although backward compatibility is being maintained across DPDK releases, code written for previous versions of the DPDK
+may require some code updates to benefit from performance and user experience enhancements provided in later DPDK releases.
-Intel® DPDK 1.6 to Intel® DPDK 1.7
-----------------------------------
+DPDK 1.7 to DPDK 1.8
+--------------------
+
+
+Intel® DPDK 1.6 to DPDK 1.7
+---------------------------
Note the following difference between 1.6 and 1.7:
--
1.8.5.3
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v3 7/8] doc: updated resolved issues with old known issues
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 0/8] doc: patch set to update release notes Siobhan Butler
` (5 preceding siblings ...)
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 6/8] doc: removed reference to Intel DPDK in Rel Notes Siobhan Butler
@ 2014-12-16 14:48 ` Siobhan Butler
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 8/8] doc: updating the list of sample apps in rel notes Siobhan Butler
` (2 subsequent siblings)
9 siblings, 0 replies; 49+ messages in thread
From: Siobhan Butler @ 2014-12-16 14:48 UTC (permalink / raw)
To: dev
Removed resolved issues from known issues section.
Added new resolved issues to resolved issues section.
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/known_issues.rst | 225 -------------------------------
doc/guides/rel_notes/resolved_issues.rst | 173 +++++++++++++++++++++++-
2 files changed, 172 insertions(+), 226 deletions(-)
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 4979e66..9fcd024 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 f47924c..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
------------------------------------------------------------------------------------
@@ -650,7 +821,7 @@ l2fwd fails to launch if the NIC is the Intel® 82571EB Gigabit Ethernet Control
------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
-| Title | 32-bit DPDK applications may fail to initialize on 64-bit OS |
+| Title | 32-bit DPDK applications may fail to initialize on 64-bit OS |
| | |
+=================================+=======================================================================================+
| Reference # | IXA00378513 |
--
1.8.5.3
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v3 8/8] doc: updating the list of sample apps in rel notes
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 0/8] doc: patch set to update release notes Siobhan Butler
` (6 preceding siblings ...)
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 7/8] doc: updated resolved issues with old known issues Siobhan Butler
@ 2014-12-16 14:48 ` Siobhan Butler
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
9 siblings, 0 replies; 49+ messages in thread
From: Siobhan Butler @ 2014-12-16 14:48 UTC (permalink / raw)
To: dev
Added new and existing names of sample apps to list of
sample apps in release notes.
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/rel_description.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/rel_notes/rel_description.rst b/doc/guides/rel_notes/rel_description.rst
index 8da53c4..49f32b9 100644
--- a/doc/guides/rel_notes/rel_description.rst
+++ b/doc/guides/rel_notes/rel_description.rst
@@ -113,10 +113,14 @@ The following is a list of DPDK documents in the suggested reading order:
* L3 Forwarding
+ * L3 Forwarding with Access Control
+
* L3 Forwarding with Power Management
* L3 Forwarding in a Virtualized Environment
+ * Link Status Interrupt
+
* Load Balancing
* Multi-process
@@ -143,6 +147,8 @@ The following is a list of DPDK documents in the suggested reading order:
* VM Power Management
+ * Distributor
+
In addition, there are some other applications that are built when the libraries are created.
The source for these applications is in the DPDK/app directory and are called:
--
1.8.5.3
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 0/8] doc: patch set to update release notes Siobhan Butler
` (7 preceding siblings ...)
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 8/8] doc: updating the list of sample apps in rel notes Siobhan Butler
@ 2014-12-17 16:47 ` Pablo de Lara
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 1/8] doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes Pablo de Lara
` (7 more replies)
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
9 siblings, 8 replies; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:47 UTC (permalink / raw)
To: dev
New Features section:
- Removed 1.7 New Features
- Added 1.8.0 New Features
Supported Features section:
- Added 1.7 features to Supported Features
Known Issues:
- Added devices to Known issue "Not all varients of supported NIC types have been used in testing"
- Removed known issue 6.29 "Double VLAN not working on 40GbE Ethnet Controller" as resolved
Resolved issues:
- Added known issue 6.29 to resolved issues
Removed references across all sections to Intel DPDK where no longer relevant.
Added new sample apps to sample apps list in release notes.
Moved issues newly resolved from known issues to resolved issues.
Removed Intel Licensing Appendix A as no longer relevant.
Siobhan Butler (8):
doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes
doc: added new features to release notes
doc: added to known issue 6.10 and removed fixed issue 6.29 from
rel_notes
doc: moved known issue 6.29 to resolved issues in rel notes
doc: remove appendix a from release notes
doc: removed reference to Intel DPDK in Rel Notes
doc: updated resolved issues with old known issues
doc: updating the list of sample apps in rel notes
doc/guides/rel_notes/appendices.rst | 324 ----------------------------
doc/guides/rel_notes/faq.rst | 14 +-
doc/guides/rel_notes/index.rst | 44 ----
doc/guides/rel_notes/known_issues.rst | 281 ++----------------------
doc/guides/rel_notes/new_features.rst | 25 ++-
doc/guides/rel_notes/rel_description.rst | 42 ++--
doc/guides/rel_notes/resolved_issues.rst | 271 ++++++++++++++++++++---
doc/guides/rel_notes/supported_features.rst | 32 ++-
doc/guides/rel_notes/supported_os.rst | 2 +-
doc/guides/rel_notes/updating_apps.rst | 12 +-
10 files changed, 331 insertions(+), 716 deletions(-)
delete mode 100644 doc/guides/rel_notes/appendices.rst
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 1/8] doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
@ 2014-12-17 16:47 ` Pablo de Lara
2014-12-18 15:17 ` Iremonger, Bernard
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 2/8] doc: added new features to release notes Pablo de Lara
` (6 subsequent siblings)
7 siblings, 1 reply; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:47 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/new_features.rst | 17 -----------------
doc/guides/rel_notes/supported_features.rst | 22 ++++++++++++++++++++++
2 files changed, 22 insertions(+), 17 deletions(-)
diff --git a/doc/guides/rel_notes/new_features.rst b/doc/guides/rel_notes/new_features.rst
index 568d0c9..a93aa3c 100644
--- a/doc/guides/rel_notes/new_features.rst
+++ b/doc/guides/rel_notes/new_features.rst
@@ -31,22 +31,5 @@
New Features
============
-* Packet Distributor library for dynamic, single-packet at a time, load balancing
-
-* IP fragmentation and reassembly library
-
-* Support for IPv6 in IP fragmentation and reassembly sample applications
-
-* Support for VFIO for mapping BARs and setting up interrupts
-
-* Link Bonding PMD Library supporting round-robin, active backup, balance(layer 2, layer 2+3, and layer 3+4) and broadcast bonding modes
-
-* Support zero copy mode RX/TX in user space vhost sample
-
-* Support multiple queues in virtio-net PMD
-
-* Support for Intel® 40GbE Controllers
-
-* Support NIC filters in addition to flow director for Intel® 1GbE and 10GbE Controllers
For further features supported in this release, see Chapter 3 Supported Features.
diff --git a/doc/guides/rel_notes/supported_features.rst b/doc/guides/rel_notes/supported_features.rst
index c51eb26..7efeff3 100644
--- a/doc/guides/rel_notes/supported_features.rst
+++ b/doc/guides/rel_notes/supported_features.rst
@@ -31,6 +31,28 @@
Supported Features
==================
+* Packet Distributor library for dynamic, single-packet at a time, load balancing
+
+* IP fragmentation and reassembly library
+
+* Support for IPv6 in IP fragmentation and reassembly sample applications
+
+* Support for VFIO for mapping BARs and setting up interrupts
+
+* Link Bonding PMD Library supporting round-robin, active backup, balance(layer 2, layer 2+3, and layer 3+4) and broadcast bonding modes
+
+* Support zero copy mode RX/TX in user space vhost sample
+
+* Support multiple queues in virtio-net PMD
+
+* Support for Intel 40GbE Controllers:
+
+ * Intel(R) XL710 40 Gigabit Ethernet Controller
+
+ * Intel(R) X710 40 Gigabit Ethernet Controller
+
+* Support NIC filters in addition to flow director for Intel� 1GbE and 10GbE Controllers
+
* Virtualization (KVM)
* Userspace vhost switch:
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 2/8] doc: added new features to release notes
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 1/8] doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes Pablo de Lara
@ 2014-12-17 16:47 ` Pablo de Lara
2014-12-18 15:18 ` Iremonger, Bernard
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 3/8] doc: added to known issue 6.10 and removed fixed issue 6.29 from rel_notes Pablo de Lara
` (5 subsequent siblings)
7 siblings, 1 reply; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:47 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/new_features.rst | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/doc/guides/rel_notes/new_features.rst b/doc/guides/rel_notes/new_features.rst
index a93aa3c..00895ce 100644
--- a/doc/guides/rel_notes/new_features.rst
+++ b/doc/guides/rel_notes/new_features.rst
@@ -30,6 +30,30 @@
New Features
============
+* Link Bonding
+ * Support for 802.3ad link aggregation (mode 4) and transmit load balancing (mode 5) to the link bonding library.
+
+ * Support for registration of link status change callbacks with link bonding devices.
+
+ * Support for slaves devices which do not support link status change interrupts in the link bonding library via a link status polling mechanism.
+
+* Poll Mode Driver - 40 GbE Controllers (librte_pmd_i40e)
+
+ * Support for Flow Director
+
+ * Support for ethertype filter
+
+ * Support RSS in VF
+
+ * Support configuring redirection table with different size from 1GbE and 10 GbE
+
+ - 128/512 entries of 40GbE PF
+
+ - 64 entries of 40GbE VF
+
+ * Support configuring hash functions
+
+* Packet Distributor Sample Application
For further features supported in this release, see Chapter 3 Supported Features.
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* Re: [dpdk-dev] [PATCH v4 2/8] doc: added new features to release notes
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 2/8] doc: added new features to release notes Pablo de Lara
@ 2014-12-18 15:18 ` Iremonger, Bernard
0 siblings, 0 replies; 49+ messages in thread
From: Iremonger, Bernard @ 2014-12-18 15:18 UTC (permalink / raw)
To: De Lara Guarch, Pablo, dev
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> Sent: Wednesday, December 17, 2014 4:48 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v4 2/8] doc: added new features to release notes
>
> From: Siobhan Butler <siobhan.a.butler@intel.com>
>
> Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
I have applied the patch to my tree next/dpdk-doc.
^ permalink raw reply [flat|nested] 49+ messages in thread
* [dpdk-dev] [PATCH v4 3/8] doc: added to known issue 6.10 and removed fixed issue 6.29 from rel_notes
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 1/8] doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes Pablo de Lara
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 2/8] doc: added new features to release notes Pablo de Lara
@ 2014-12-17 16:47 ` Pablo de Lara
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 4/8] doc: moved known issue 6.29 to resolved issues in rel notes Pablo de Lara
` (4 subsequent siblings)
7 siblings, 0 replies; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:47 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/known_issues.rst | 36 ++++++-----------------------------
1 file changed, 6 insertions(+), 30 deletions(-)
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index d26dcfa..1cfc977 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -338,6 +338,12 @@ Not all variants of supported NIC types have been used in testing
| | |
| | The NIC device identifiers used during testing: |
| | |
+| | * Intel(R) Ethernet Controller XL710 for 40GbE QSFP+ [8086:1584] |
+| | |
+| | * Intel(R) Ethernet Controller XL710 for 40GbE QSFP+ [8086:1583] |
+| | |
+| | * Intel(R) Ethernet Controller X710 for 10GbE SFP+ [8086:1572] |
+| | |
| | * Intel® 82576 Gigabit Ethernet Controller [8086:10c9] |
| | |
| | * Intel® 82576 Quad Copper Gigabit Ethernet Controller [8086:10e8] |
@@ -940,36 +946,6 @@ Ethertype filter could receive other packets (non-assigned) in Niantic
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-Double VLAN does not work on Intel® 40G ethernet controller
------------------------------------------------------------
-
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Title | Double VLAN does not work on Intel® 40G ethernet controller |
-| | |
-+================================+======================================================================================+
-| Reference # | IXA00386480 |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | On Intel® 40G Ethernet Controller: |
-| | |
-| | Double VLAN does not work. This was confirmed a firmware issue which will be fixed |
-| | in later versions of firmware. |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | After setting double vlan to be enabled on a port, no packets can be transmitted out |
-| | on that port. |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Resolution/ Workaround | None |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Affected Environment/ Platform | All |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Driver/Module | Poll Mode Driver (PMD) |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-
Cannot set link speed on Intel® 40G ethernet controller
-------------------------------------------------------
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 4/8] doc: moved known issue 6.29 to resolved issues in rel notes
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
` (2 preceding siblings ...)
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 3/8] doc: added to known issue 6.10 and removed fixed issue 6.29 from rel_notes Pablo de Lara
@ 2014-12-17 16:47 ` Pablo de Lara
2014-12-18 15:20 ` Iremonger, Bernard
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 5/8] doc: remove appendix a from release notes Pablo de Lara
` (3 subsequent siblings)
7 siblings, 1 reply; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:47 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/resolved_issues.rst | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/doc/guides/rel_notes/resolved_issues.rst b/doc/guides/rel_notes/resolved_issues.rst
index f9ddb7f..66afc25 100644
--- a/doc/guides/rel_notes/resolved_issues.rst
+++ b/doc/guides/rel_notes/resolved_issues.rst
@@ -1192,3 +1192,33 @@ Packet reception issues when virtualization is enabled
| Driver/Module | Poll mode drivers |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
+
+
+
+Double VLAN does not work on Intel� 40GbE ethernet contoller
+------------------------------------------------------------
+
++---------------------------------+---------------------------------------------------------------------------------------+
+| Title | Double VLAN does not work on Intel� 40GbE ethernet controller |
+| | |
++=================================+=======================================================================================+
+| Reference # | IXA00369908 |
+| | |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Description | On Intel(R) 40 GbE ethernet controller double VLAN does not work. |
+| | This was confirmed as a Firmware issue which will be fixed in later versions of |
+| | firmware. |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Implication | After setting double vlan to be enabled on a port, no packets can be transmitted out |
+| | on that port. |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Resolution/Workaround | Resolved in latest release with firmware upgrade. |
+| | |
+| | |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Affected Environment/Platform | All |
+| | |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Driver/Module | Poll mode drivers |
+| | |
++---------------------------------+---------------------------------------------------------------------------------------+
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 5/8] doc: remove appendix a from release notes
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
` (3 preceding siblings ...)
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 4/8] doc: moved known issue 6.29 to resolved issues in rel notes Pablo de Lara
@ 2014-12-17 16:47 ` Pablo de Lara
2014-12-18 15:21 ` Iremonger, Bernard
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 6/8] doc: removed reference to Intel DPDK in Rel Notes Pablo de Lara
` (2 subsequent siblings)
7 siblings, 1 reply; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:47 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Removing Appendix A from Release Notes as Intel Licensing information is
no longer relevant in this document.
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/appendices.rst | 324 ------------------------------------
doc/guides/rel_notes/index.rst | 44 -----
2 files changed, 368 deletions(-)
delete mode 100644 doc/guides/rel_notes/appendices.rst
diff --git a/doc/guides/rel_notes/appendices.rst b/doc/guides/rel_notes/appendices.rst
deleted file mode 100644
index 6dec2e1..0000000
--- a/doc/guides/rel_notes/appendices.rst
+++ /dev/null
@@ -1,324 +0,0 @@
-.. BSD LICENSE
- Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
- All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
-
- * Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
- * Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in
- the documentation and/or other materials provided with the
- distribution.
- * Neither the name of Intel Corporation nor the names of its
- contributors may be used to endorse or promote products derived
- from this software without specific prior written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-Appendix A Intel® DPDK License Overview
-=========================================
-
-
-The following describes the various licenses used by the Intel® Data Plane Development Kit (Intel® DPDK).
-The purpose of the Intel® DPDK is to prove the abilities of the Intel® architecture processors and to provide users with a strong set of examples, libraries and proof points.
-By placing the majority of this software under the BSD License, users may choose to use the Intel® as is, parts of it, or just the ideas for their programs.
-All code may be modified by the user to suit their project needs and requirements.
-
-.. note::
-
- The license in each source file takes precedence over this document, and should be used as the definitive license for that file.
- All users should seek their legal team's guidance with respect to the licensing used by the Intel® DPDK.
-
-
-
-The following table lists those files (or libraries) that are not under a BSD License. In some cases, these files are part of the standard Intel® DPDK release package,
-and in other cases may be a separate package that requires a separate download to be added to the Intel® DPDK. This document spells out those cases where possible.
-
-The sections following the table provide the various licenses used. Please note that copyright notices may change overtime.
-It is the responsibility of all users to understand these licenses and seek their legal team's guidance.
-
-The use of the GPLv2 License is confined to files in kernel loadable modules.
-
-The use of the Dual BSD/LGPLv2 License and Dual BSD/GPL License allows use with either free/open source software or with proprietary software in userspace.
-
-
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| File | Description | License |
-| | | |
-+===================================================+======================================================================================================================+======================================+
-| igb_uio.c | **1st Released** | GPLv2 License Information |
-| | : 1.0 | |
-| | | |
-| | **Location** | |
-| | : | |
-| | DPDK/lib/librte_eal/linuxapp/igb_uio/ | |
-| | | |
-| | **Description** | |
-| | : This file is used for a kernel loadable module which is responsible for unbinding NICs from the Linux kernel | |
-| | and binding them to the Intel® DPDK | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| kni_dev.h kni_ethtool.c kni_misc.c kni_net.c | **1st Released** | GPLv2 License Information |
-| | : 1.3 | |
-| | | |
-| | **Location** | |
-| | : DPDK/lib/librte_eal/linuxapp/kni/ | |
-| | | |
-| | **Description** | |
-| | : The KNI kernel loadable module is a standard net driver which allows Intel DPDK Linux userspace applications | |
-| | to exchange packets/data with the Linux kernel. | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| rte_kni_common.h | **1st Released** | Dual BSD/LGPLv2 License Information |
-| | : 1.3 | |
-| | | |
-| | **Location** | |
-| | : DPDK/lib/librte_eal/linuxapp/eal/include/exec-env/ | |
-| | | |
-| | **Description** | |
-| | : The KNI header files is utilized by both the Intel DPDK userspace application and the KNI kernel loadable module | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| All files under this directory are for the | **1st Released** | GPLv2 License Information |
-| ethtool functionality. | : 1.3 | |
-| | | |
-| | **Location** | |
-| | : DPDK/lib/librte_eal/linuxapp/kni/ethtool | |
-| | | |
-| | **Description** | |
-| | : The igb and ixgbe drivers for the Ethtool function available with the KNI kernel loadable. | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| rte_pci_dev_ids.h | **1st Released** | Dual BSD/GPL License Information |
-| | : 1.3 | |
-| | | |
-| | **Location** | |
-| | : DPDK/lib/librte_eal/common/include | |
-| | | |
-| | **Description** | |
-| | : Contains the PCI device ids for all devices. | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-
-Added rte_dom0_mm.h file for Dual BSD/LGPLv2 License information:
-
-rte_dom0_mm.h 1st Released 1.6.0
-
-Location: DPDK/lib/librte_eal/eal/include/exec-env/
-
-Description: The Dom0 header file is utilized by both the Intel® DPDK userspace application and the Dom0 kernel loadable module
-
-Added dom0_mm_misc.h and dom0_mm_misc.c file for Dual BSD/GPLv2 License Information:
-
-dom0_mm_dev.h 1st Released 1.6.0
-
-dom0_mm_dev.c Location: DPDK/lib/librte_eal/linuxapp/xen_dom0
-
-Description: The Dom0 memory management kernel loadable module is a misc device driver which is used to facilitate allocating and mapping via an **IOCTL** (allocation) and **MMAP** (mapping).
-
-
-A.1 BSD License
----------------
-
-.. code-block:: c
-
- /*-
- * BSD LICENSE
- *
- * Copyright(c) 2010-2012 Intel Corporation. All rights reserved.
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * * Redistributions of source code must retain the above copyright
- * notice, this list of conditions and the following disclaimer.
- * * Redistributions in binary form must reproduce the above copyright
- * notice, this list of conditions and the following disclaimer in
- * the documentation and/or other materials provided with the
- * distribution.
- * * Neither the name of Intel Corporation nor the names of its
- * contributors may be used to endorse or promote products derived
- * from this software without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- *
- */
-
-A.2 GPLv2 License Information
------------------------------
-
-.. code-block:: c
-
- /*-
- *
- * Copyright (c) 2010-2012, Intel Corporation
- *
- * This program is free software; you can redistribute it and/or
- * modify it under the terms of the GNU General Public License
- * as published by the Free Software Foundation; either version 2
- * of the License, or (at your option) any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
- *
-..
-
- \* GNU GPL V2: `http://www.gnu.org/licenses/old-licenses/gpl-2.0.html <http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>`_
-
-.. code-block:: c
-
- *
- */
-
-A.3 Dual BSD/LGPLv2 License Information
----------------------------------------
-
-.. code-block:: c
-
- /*
- This file is provided under a dual BSD/LGPLv2 license. When using
- or redistributing this file, you may do so under either license.
-
- GNU LESSER GENERAL PUBLIC LICENSE
-
- Copyright(c) 2007,2008,2009 Intel Corporation. All rights reserved.
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of version 2.1 of the GNU Lesser General Public License
- as published by the Free Software Foundation.
-
- This program is distributed in the hope that it will be useful, but WITHOUT ANY
- WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- PARTICULAR PURPOSE. See the GNU
- Lesser General Public License for more details.
-
- You should have received a copy of the GNU Lesser General Public License along with
- this program; if not, write to the Free Software
- Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
-
-
- Contact Information: Intel Corporation
-
- BSD LICENSE
-
- Copyright(c) 2010-2012 Intel Corporation.All rights reserved. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without modification, are
- permitted provided that the following conditions are met:
-
- Redistributions of source code must retain the above copyright notice, this list of
- conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list
- of conditions and the following disclaimer in the documentation and/or other
- materials provided with the distribution.
- Neither the name of Intel Corporation nor the names of its contributors may be used
- to endorse or promote products derived from this software without specific prior
- written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
- EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
- SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
- TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
- BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
- CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
- ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
- DAMAGE.
- */
-
-
-A.4 Dual BSD/GPL License Information
-------------------------------------
-
-.. code-block:: c
-
- /*-
- * This file is provided under a dual BSD/GPLv2 license. When using or
- * redistributing this file, you may do so under either license.
- *
- * GPL LICENSE SUMMARY
- *
- * Copyright(c) 2010-2012 Intel Corporation. All rights reserved.
- *
- * This program is free software; you can redistribute it and/or modify
- * it under the terms of version 2 of the GNU General Public License as
- * published by the Free Software Foundation.
- *
- * This program is distributed in the hope that it will be useful, but
- * WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
- * General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
- * The full GNU General Public License is included in this distribution
- * in the file called LICENSE.GPL.
- *
- * Contact Information:
- * Intel Corporation
- *
- * BSD LICENSE
- *
- * Copyright(c) 2010-2012 Intel Corporation. All rights reserved.
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * * Redistributions of source code must retain the above copyright
- * notice, this list of conditions and the following disclaimer.
- * * Redistributions in binary form must reproduce the above copyright
- * notice, this list of conditions and the following disclaimer in
- * the documentation and/or other materials provided with the
- * distribution.
- * * Neither the name of Intel Corporation nor the names of its
- * contributors may be used to endorse or promote products derived
- * from this software without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- *
- */
diff --git a/doc/guides/rel_notes/index.rst b/doc/guides/rel_notes/index.rst
index e9a3d21..69e59d4 100644
--- a/doc/guides/rel_notes/index.rst
+++ b/doc/guides/rel_notes/index.rst
@@ -35,49 +35,6 @@ Package Version: 1.7
|today|
-INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS.
-NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT.
-EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY,
-RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT,
-COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
-
-A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death.
-SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES,
-AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY,
-ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN,
-MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS.
-
-Intel may make changes to specifications and product descriptions at any time, without notice.
-Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined".
-Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.
-The information here is subject to change without notice.
-Do not finalize a design with this information.
-
-The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications.
-Current characterized errata are available on request.
-
-Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
-
-Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling
-1-800-548-4725, or go to:
-`http://www.intel.com/design/literature.htm <http://www.intel.com/design/literature.htm>`_
-
-Any software source code reprinted in this document is furnished for informational purposes only and may only be used or copied and no license, express or implied, by estoppel or otherwise,
-to any of the reprinted source code is granted by this document.
-
-Code Names are only for use by Intel to identify products, platforms, programs, services, etc. ("products") in development by
-Intel that have not been made commercially available to the public, i.e., announced, launched or shipped. They are never to be used as "commercial" names for products.
-Also, they are not intended to function as trademarks.
-
-See Appendix A for an overview of the applicable software licenses.
-
-Intel, the Intel logo, Intel Core and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
-
-\*Other names and brands may be claimed as the property of others.
-
-Copyright © 2012-2014 , Intel Corporation. All rights reserved.
-
-
Contents
.. toctree::
@@ -92,4 +49,3 @@ Contents
known_issues
resolved_issues
faq
- appendices
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* Re: [dpdk-dev] [PATCH v4 5/8] doc: remove appendix a from release notes
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 5/8] doc: remove appendix a from release notes Pablo de Lara
@ 2014-12-18 15:21 ` Iremonger, Bernard
0 siblings, 0 replies; 49+ messages in thread
From: Iremonger, Bernard @ 2014-12-18 15:21 UTC (permalink / raw)
To: De Lara Guarch, Pablo, dev
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> Sent: Wednesday, December 17, 2014 4:48 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v4 5/8] doc: remove appendix a from release notes
>
> From: Siobhan Butler <siobhan.a.butler@intel.com>
>
> Removing Appendix A from Release Notes as Intel Licensing information is no longer relevant in this
> document.
>
> Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
I have applied the patch to my tree next/dpdk-doc.
^ permalink raw reply [flat|nested] 49+ messages in thread
* [dpdk-dev] [PATCH v4 6/8] doc: removed reference to Intel DPDK in Rel Notes
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
` (4 preceding siblings ...)
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 5/8] doc: remove appendix a from release notes Pablo de Lara
@ 2014-12-17 16:47 ` Pablo de Lara
2014-12-18 15:22 ` Iremonger, Bernard
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 7/8] doc: updated resolved issues with old known issues Pablo de Lara
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 8/8] doc: updating the list of sample apps in rel notes Pablo de Lara
7 siblings, 1 reply; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:47 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Removed multiple references to Intel(R) DPDK where no longer
relevant.
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/faq.rst | 14 +++---
doc/guides/rel_notes/known_issues.rst | 30 ++++++-------
doc/guides/rel_notes/rel_description.rst | 36 ++++++---------
doc/guides/rel_notes/resolved_issues.rst | 70 ++++++++++++++---------------
doc/guides/rel_notes/supported_features.rst | 10 ++---
doc/guides/rel_notes/supported_os.rst | 2 +-
doc/guides/rel_notes/updating_apps.rst | 12 +++--
7 files changed, 85 insertions(+), 89 deletions(-)
diff --git a/doc/guides/rel_notes/faq.rst b/doc/guides/rel_notes/faq.rst
index dfc34e6..054db10 100644
--- a/doc/guides/rel_notes/faq.rst
+++ b/doc/guides/rel_notes/faq.rst
@@ -36,7 +36,7 @@ When running the test application, I get “EAL: map_all_hugepages(): open faile
This is most likely due to the test application not being run with sudo to promote the user to a superuser.
Alternatively, applications can also be run as regular user.
-For more information, please refer to *Intel® DPDK Getting Started Guide*.
+For more information, please refer to *DPDK Getting Started Guide*.
If I want to change the number of TLB Hugepages allocated, how do I remove the original pages allocated?
--------------------------------------------------------------------------------------------------------
@@ -49,7 +49,7 @@ If you look in the directory, you will see n number of 2M pages files. If you sp
These are then placed in memory segments to get contiguous memory.
If you need to change the number of pages, it is easier to first remove the pages. The tools/setup.sh script provides an option to do this.
-See the “Quick Start Setup Script” section in the *Intel® DPDK Getting Started Guide* for more information.
+See the “Quick Start Setup Script” section in the *DPDK Getting Started Guide* for more information.
If I execute “l2fwd -c f -m 64 –n 3 -- -p 3”, I get the following output, indicating that there are no socket 0 hugepages to allocate the mbuf and ring structures to?
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -59,14 +59,14 @@ I have set up a total of 1024 Hugepages (that is, allocated 512 2M pages to each
The -m command line parameter does not guarantee that huge pages will be reserved on specific sockets. Therefore, allocated huge pages may not be on socket 0.
To request memory to be reserved on a specific socket, please use the --socket-mem command-line parameter instead of -m.
-I am running a 32-bit Intel® DPDK application on a NUMA system, and sometimes the application initializes fine but cannot allocate memory. Why is that happening?
+I am running a 32-bit DPDK application on a NUMA system, and sometimes the application initializes fine but cannot allocate memory. Why is that happening?
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
32-bit applications have limitations in terms of how much virtual memory is available, hence the number of hugepages they are able to allocate is also limited (1 GB per page size).
If your system has a lot (>1 GB per page size) of hugepage memory, not all of it will be allocated.
Due to hugepages typically being allocated on a local NUMA node, the hugepages allocation the application gets during the initialization depends on which
NUMA node it is running on (the EAL does not affinitize cores until much later in the initialization process).
-Sometimes, the Linux OS runs the Intel® DPDK application on a core that is located on a different NUMA node from Intel® DPDK master core and
+Sometimes, the Linux OS runs the DPDK application on a core that is located on a different NUMA node from DPDK master core and
therefore all the hugepages are allocated on the wrong socket.
To avoid this scenario, either lower the amount of hugepage memory available to 1 GB per page size (or less), or run the application with taskset
@@ -102,7 +102,7 @@ Traditionally, there is a trade-off between throughput and latency. An applicati
but the end-to-end latency of an average packet typically increases as a result.
Similarly, the application can be tuned to have, on average, a low end-to-end latency at the cost of lower throughput.
-To achieve higher throughput, the Intel® DPDK attempts to aggregate the cost of processing each packet individually by processing packets in bursts.
+To achieve higher throughput, the DPDK attempts to aggregate the cost of processing each packet individually by processing packets in bursts.
Using the testpmd application as an example, the “burst” size can be set on the command line to a value of 16 (also the default value).
This allows the application to request 16 packets at a time from the PMD.
The testpmd application then immediately attempts to transmit all the packets that were received, in this case, all 16 packets.
@@ -144,11 +144,11 @@ For best performance with NUMA disabled, only one socket should be populated.
I am getting errors about not being able to open files. Why?
------------------------------------------------------------
-As the Intel® DPDK operates, it opens a lot of files, which can result in reaching the open files limits, which is set using the ulimit command or in the limits.conf file.
+As the DPDK operates, it opens a lot of files, which can result in reaching the open files limits, which is set using the ulimit command or in the limits.conf file.
This is especially true when using a large number (>512) of 2 MB huge pages. Please increase the open file limit if your application is not able to open files.
This can be done either by issuing a ulimit command or editing the limits.conf file. Please consult Linux* manpages for usage information.
-Does my kernel require patching to run the Intel® DPDK?
+Does my kernel require patching to run the DPDK?
-------------------------------------------------------
Any kernel greater than version 2.6.33 can be used without any patches applied. The following kernels may require patches to provide hugepage support:
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 1cfc977..0107f9d 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -31,7 +31,7 @@
Known Issues and Limitations
============================
-This section describes known issues with the Intel® DPDK software, Release 1.6.0.
+This section describes known issues with the DPDK software, Release 1.8.0.
Pause Frame Forwarding does not work properly on igb
----------------------------------------------------
@@ -112,13 +112,13 @@ Vhost-xen cannot detect Domain U application exit on Xen version 4.0.1
| Reference # | IXA00168947 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | When using Intel® DPDK applications on Xen 4.0.1, e.g. TestPMD Sample Application, |
+| 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 |
+| | 4.0.1 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Resolution | |
@@ -154,7 +154,7 @@ Virtio incorrect header length used if MSI-X is disabled by kernel driver
| | specification and resolves to the VIRTIO_NET_F_MAC feature instead. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | The Intel® DPDK kernel driver will enable MSI-X by default, |
+| 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”. |
@@ -425,13 +425,13 @@ Unstable system performance across application executions with 2MB pages
| Reference # | IXA00372346 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | The performance of an Intel® DPDK application may vary across executions of an |
+| 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 Intel® DPDK applications is encountered.|
+| 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. |
@@ -536,7 +536,7 @@ PMD does not work with --no-huge EAL command line parameter
| Reference # | IXA00373461 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | Currently, the Intel® DPDK does not store any information about memory allocated by |
+| Description | Currently, the DPDK does not store any information about memory allocated by |
| | malloc() (for example, NUMA node, physical address), hence PMD drivers do not work |
| | when the --no-huge command line parameter is supplied to EAL. |
| | |
@@ -547,7 +547,7 @@ PMD does not work with --no-huge EAL command line parameter
| Resolution/ Workaround | Use huge page memory or use VFIO to map devices. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Affected Environment/ Platform | Systems running the Intel® DPDK on Linux |
+| Affected Environment/ Platform | Systems running the DPDK on Linux |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Driver/Module | Poll Mode Driver (PMD) |
@@ -701,24 +701,24 @@ Discrepancies between statistics reported by different NICs
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-Error reported opening files on Intel® DPDK initialization
-----------------------------------------------------------
+Error reported opening files on DPDK initialization
+---------------------------------------------------
+--------------------------------+--------------------------------------------------------------------------------------+
-| Title | Error reported opening files on Intel® DPDK initialization |
+| Title | Error reported opening files on DPDK initialization |
| | |
+================================+======================================================================================+
| Reference # | 91 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | On Intel® DPDK application startup, errors may be reported when opening files as |
+| Description | On DPDK application startup, errors may be reported when opening files as |
| | part of the initialization process. This occurs if a large number, for example, 500 |
| | or more, or if hugepages are used, due to the per-process limit on the number of |
| | open files. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | The Intel® DPDK application may fail to run. |
+| Implication | The DPDK application may fail to run. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Resolution/ Workaround | If using 2 MB hugepages, consider switching to a fewer number of 1 GB pages. |
@@ -890,11 +890,11 @@ GCC might generate Intel® AVX instructions forprocessors without Intel® AVX su
| Reference # | IXA00382439 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | When compiling Intel® DPDK (and any Intel® DPDK app), gcc may generate Intel® AVX |
+| Description | When compiling Intel® DPDK (and any DPDK app), gcc may generate Intel® AVX |
| | instructions, even when the processor does not support Intel® AVX. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | Any Intel® DPDK app might crash while starting up. |
+| Implication | Any DPDK app might crash while starting up. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Resolution/ Workaround | Either compile using icc or set EXTRA_CFLAGS=’-O3’ prior to compilation. |
diff --git a/doc/guides/rel_notes/rel_description.rst b/doc/guides/rel_notes/rel_description.rst
index d159b3c..8da53c4 100644
--- a/doc/guides/rel_notes/rel_description.rst
+++ b/doc/guides/rel_notes/rel_description.rst
@@ -32,22 +32,14 @@ Description of Release
======================
These release notes cover the new features,
-fixed bugs and known issues for Intel® Data Plane Development Kit (Intel® DPDK) release version 1.7.0.
+fixed bugs and known issues for Data Plane Development Kit (DPDK) release version 1.7.0.
-For instructions on compiling and running the release, see the *Intel® DPDK Getting Started Guide*.
+For instructions on compiling and running the release, see the *DPDK Getting Started Guide*.
-Important Note
---------------
+Using DPDK Upgrade Patches
+--------------------------
-All Intel® DPDK questions and technical problems including those regarding the Ethernet* Controllers for the Poll Mode Driver should be reported through the Intel® Premier Support site
-`http://premier.intel.com/premier <http://premier.intel.com/premier>`_
-or access your IBL account and click the **Intel® Premier Support** link to enter issues under the Product Name “Data Plane Development Kit (DPDK)”,
-which are then routed to our support team.
-
-Using Intel® DPDK Upgrade Patches
----------------------------------
-
-For minor updates to the main Intel® DPDK releases, the software may be made available both as a new full package and as a patch file to be applied to the previously released package.
+For minor updates to the main DPDK releases, the software may be made available both as a new full package and as a patch file to be applied to the previously released package.
In the latter case, the following commands should be used to apply the patch on top of the already-installed package for the previous release:
.. code-block:: console
@@ -55,7 +47,7 @@ In the latter case, the following commands should be used to apply the patch on
# cd $RTE_SDK
# patch –p1 < /path/to/patch/file
-Once the patch has been applied cleanly, the Intel® DPDK can be recompiled and used as before (described in the *Intel® DPDK Getting Started Guide*).
+Once the patch has been applied cleanly, the DPDK can be recompiled and used as before (described in the *DPDK Getting Started Guide*).
.. note::
@@ -65,25 +57,25 @@ Once the patch has been applied cleanly, the Intel® DPDK can be recompiled and
Documentation Roadmap
---------------------
-The following is a list of Intel® DPDK documents in the suggested reading order:
+The following is a list of DPDK documents in the suggested reading order:
* **Release Notes**
(this document): Provides release-specific information, including supported features, limitations, fixed issues, known issues and so on.
Also, provides the answers to frequently asked questions in FAQ format.
* **Getting Started Guide**
- : Describes how to install and configure the Intel® DPDK software; designed to get users up and running quickly with the software.
+ : Describes how to install and configure the DPDK software; designed to get users up and running quickly with the software.
* **FreeBSD* Getting Started Guide**
- : A document describing the use of the Intel® DPDK with FreeBSD* has been added in Intel® DPDK Release 1.6.0.
- Refer to this guide for installation and configuration instructions to get started using the Intel® DPDK with FreeBSD*.
+ : A document describing the use of the DPDK with FreeBSD* has been added in DPDK Release 1.6.0.
+ Refer to this guide for installation and configuration instructions to get started using the DPDK with FreeBSD*.
* **Programmer's Guide**
: Describes:
* The software architecture and how to use it (through examples), specifically in a Linux* application (linuxapp) environment
- * The content of the Intel® DPDK, the build system (including the commands that can be used in the root Intel® DPDK Makefile to build the development kit and an application)
+ * The content of the DPDK, the build system (including the commands that can be used in the root DPDK Makefile to build the development kit and an application)
and guidelines for porting an application
* Optimizations used in the software and those that should be considered for new development
@@ -91,7 +83,7 @@ The following is a list of Intel® DPDK documents in the suggested reading order
A glossary of terms is also provided.
* **API Reference**
- : Provides detailed information about Intel® DPDK functions, data structures and other programming constructs.
+ : Provides detailed information about DPDK functions, data structures and other programming constructs.
* **Sample Applications User Guide**
: Describes a set of sample applications. Each chapter describes a sample application that showcases specific functionality and provides instructions on how to compile,
@@ -160,11 +152,11 @@ The following is a list of Intel® DPDK documents in the suggested reading order
Once the libraries are created, they can be found in the build/app directory.
- * The test application provides a variety of specific tests for the various functions in the Intel® DPDK.
+ * The test application provides a variety of specific tests for the various functions in the DPDK.
* The testpmd application provides a number of different packet throughput tests and examples of features such as
how to use the Flow Director found in the Intel® 82599 10 Gigabit Ethernet Controller.
- The testpmd application is documented in the *Intel® DPDK Testpmd Application Note* (525362).
+ The testpmd application is documented in the *DPDK Testpmd Application Note* (525362).
The test application is not currently documented.
However, you should be able to run and use test application with the command line help that is provided in the application.
diff --git a/doc/guides/rel_notes/resolved_issues.rst b/doc/guides/rel_notes/resolved_issues.rst
index 66afc25..16e1026 100644
--- a/doc/guides/rel_notes/resolved_issues.rst
+++ b/doc/guides/rel_notes/resolved_issues.rst
@@ -200,7 +200,7 @@ Device initialization failure with Intel® Ethernet Server Adapter X520-T2
| Reference # | 55 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Description | If this device is bound to the Linux kernel IXGBE driver when the Intel® DPDK is |
+| Description | If this device is bound to the Linux kernel IXGBE driver when the DPDK is |
| | initialized, DPDK is initialized, the device initialization fails with error code -17 |
| | “IXGBE_ERR_PHY_ADDR_INVALID”. |
| | |
@@ -208,7 +208,7 @@ Device initialization failure with Intel® Ethernet Server Adapter X520-T2
| Implication | The device is not initialized and cannot be used by an application. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution/Workaround | Introduced a small delay in device initialization to allow Intel® DPDK to always find |
+| Resolution/Workaround | Introduced a small delay in device initialization to allow DPDK to always find |
| | the device. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -219,11 +219,11 @@ Device initialization failure with Intel® Ethernet Server Adapter X520-T2
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-Intel® DPDK kernel module is incompatible with Linux kernel version 3.3
------------------------------------------------------------------------
+DPDK kernel module is incompatible with Linux kernel version 3.3
+----------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
-| Title | Intel® DPDK kernel module is incompatible with Linux kernel version 3.3 |
+| Title | DPDK kernel module is incompatible with Linux kernel version 3.3 |
| | |
+=================================+=======================================================================================+
| Reference # | IXA00373232 |
@@ -430,7 +430,7 @@ Port not found issue with Intel® 82580 Gigabit Ethernet Controller
+---------------------------------+---------------------------------------------------------------------------------------+
| Description | After going through multiple driver unbind/bind cycles, an Intel® 82580 |
| | Ethernet Controller port may no longer be found and initialized by the |
-| | Intel® DPDK. |
+| | DPDK. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Implication | The port will be unusable. |
@@ -506,8 +506,8 @@ Promiscuous mode for 82580 NICs can only be enabled after a call to rte_eth_dev_
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-Incorrect CPU socket information reported in /proc/cpuinfo can prevent the Intel® DPDK from running
----------------------------------------------------------------------------------------------------
+Incorrect CPU socket information reported in /proc/cpuinfo can prevent the DPDK from running
+--------------------------------------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
| Title | Incorrect CPU socket information reported in /proc/cpuinfo can prevent the Intel® |
@@ -517,14 +517,14 @@ Incorrect CPU socket information reported in /proc/cpuinfo can prevent the Intel
| Reference # | 63 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Description | The Intel® DPDK users information supplied by the Linux kernel to determine the |
+| Description | The DPDK users information supplied by the Linux kernel to determine the |
| | hardware properties of the system being used. On rare occasions, information supplied |
| | by /proc/cpuinfo does not match that reported elsewhere. In some cases, it has been |
| | observed that the CPU socket numbering given in /proc/cpuinfo is incorrect and this |
-| | can prevent Intel® DPDK from operating. |
+| | can prevent DPDK from operating. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Implication | The Intel® DPDK cannot run on systems where /proc/cpuinfo does not report the correct |
+| Implication | The DPDK cannot run on systems where /proc/cpuinfo does not report the correct |
| | CPU socket topology. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -578,7 +578,7 @@ L3FWD-VF might lose CRC bytes
| Description | Currently, the CRC stripping configuration does not affect the VF driver. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Implication | Packets transmitted by the Intel® DPDK in the VM may be lacking 4 bytes (packet CRC). |
+| Implication | Packets transmitted by the DPDK in the VM may be lacking 4 bytes (packet CRC). |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Resolution/ Workaround | Set “strip_crc” to 1 in the sample applications that use the VF PMD. |
@@ -591,8 +591,8 @@ L3FWD-VF might lose CRC bytes
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-32-bit Intel® DPDK sample applications fails when using more than one 1 GB hugepage
------------------------------------------------------------------------------------
+32-bit DPDK sample applications fails when using more than one 1 GB hugepage
+----------------------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
| Title | 32-bit Intel® DPDK sample applications fails when using more than one 1 GB hugepage |
@@ -646,11 +646,11 @@ l2fwd fails to launch if the NIC is the Intel® 82571EB Gigabit Ethernet Control
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-32-bit Intel® DPDK applications may fail to initialize on 64-bit OS
--------------------------------------------------------------------
+32-bit DPDK applications may fail to initialize on 64-bit OS
+------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
-| Title | 32-bit Intel® DPDK applications may fail to initialize on 64-bit OS |
+| Title | 32-bit DPDK applications may fail to initialize on 64-bit OS |
| | |
+=================================+=======================================================================================+
| Reference # | IXA00378513 |
@@ -739,12 +739,12 @@ Config file change can cause build to fail
| Reference # | IXA00369247 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Description | If a change in a config file results in some Intel® DPDK files that were needed no |
+| Description | If a change in a config file results in some DPDK files that were needed no |
| | longer being needed, the build will fail. This is because the \*.o file will still |
| | exist, and the linker will try to link it. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Implication | Intel® DPDK compilation failure |
+| Implication | DPDK compilation failure |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Resolution | The Makefile now provides instructions to clean out old kernel module object files. |
@@ -768,8 +768,8 @@ rte_cmdline library should not be used in production code due to limited testing
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Description | The rte_cmdline library provides a command line interface for use in sample |
-| | applications and test applications distributed as part of Intel® DPDK. However, it is |
-| | not validated to the same standard as other Intel® DPDK libraries. |
+| | applications and test applications distributed as part of DPDK. However, it is |
+| | not validated to the same standard as other DPDK libraries. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Implication | It may contain bugs or errors that could cause issues in production applications. |
@@ -1017,18 +1017,18 @@ EAL can silently reserve less memory than requested
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-SSH connectivity with the board may be lost when starting an Intel® DPDK application
-------------------------------------------------------------------------------------
+SSH connectivity with the board may be lost when starting a DPDK application
+----------------------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
-| Title | SSH connectivity with the board may be lost when starting an Intel® DPDK application |
+| Title | SSH connectivity with the board may be lost when starting a DPDK application |
| | |
+=================================+=======================================================================================+
| Reference # | 26 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Description | Currently, the Intel® DPDK takes over all the NICs found on the board that are |
-| | supported by the Intel® DPDK. This results in these NICs being removed from the NIC |
+| | supported by the DPDK. This results in these NICs being removed from the NIC |
| | set handled by the kernel,which has the side effect of any SSH connection being |
| | terminated. See also issue #27. |
| | |
@@ -1036,8 +1036,8 @@ SSH connectivity with the board may be lost when starting an Intel® DPDK applic
| Implication | Loss of network connectivity to board. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution | Intel® DPDK now no longer binds ports on startup. Please refer to the Getting Started |
-| | Guide for information on how to bind/unbind ports from Intel® DPDK. |
+| Resolution | DPDK now no longer binds ports on startup. Please refer to the Getting Started |
+| | Guide for information on how to bind/unbind ports from DPDK. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Affected Environment/Platform | Systems using a Intel®DPDK supported NIC for remote system access |
@@ -1065,12 +1065,12 @@ Remote network connections lost when running autotests or sample applications
| Implication | Loss of network connectivity to board when connected remotely. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution | Intel® DPDK now no longer binds ports on startup. |
+| Resolution | DPDK now no longer binds ports on startup. |
| | Please refer to the Getting Started Guide for information on how to bind/unbind ports |
-| | from Intel® DPDK. |
+| | from DPDK. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Affected Environment/Platform | Systems using a Intel® DPDK supported NIC for remote system access |
+| Affected Environment/Platform | Systems using a DPDK supported NIC for remote system access |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Driver/Module | Sample applications |
@@ -1089,10 +1089,10 @@ KNI may not work properly in a multi-process environment
+---------------------------------+---------------------------------------------------------------------------------------+
| Description | Some of the network interface operations such as, MTU change or link UP/DOWN, when |
| | executed on KNI interface, might fail in a multi-process environment, although they |
-| | are normally successful in the Intel® DPDK single process environment. |
+| | are normally successful in the DPDK single process environment. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Implication | Some network interface operations on KNI cannot be used in an Intel® DPDK |
+| Implication | Some network interface operations on KNI cannot be used in a DPDK |
| | multi-process environment. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -1119,14 +1119,14 @@ Hash library cannot be used in multi-process applications with multiple binaries
| Description | The hash function used by a given hash-table implementation is referenced in the code |
| | by way of a function pointer. This means that it cannot work in cases where the hash |
| | function is at a different location in the code segment in different processes, as is |
-| | the case where an Intel® DPDK multi-process application uses a number of different |
+| | the case where a DPDK multi-process application uses a number of different |
| | binaries, for example, the client-server multi-process example. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Implication | The Hash library will not work if shared by multiple processes. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution/Workaround | New API was added for multiprocess scenario. Please refer to Intel® DPDK Programmer’s |
+| Resolution/Workaround | New API was added for multiprocess scenario. Please refer to DPDK Programmer’s |
| | Guide for more information. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -1182,7 +1182,7 @@ Packet reception issues when virtualization is enabled
| Implication | An application requiring packet transmission or reception will not function. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution/Workaround | Intel® DPDK Poll Mode Driver now has the ability to map correct physical addresses to |
+| Resolution/Workaround | DPDK Poll Mode Driver now has the ability to map correct physical addresses to |
| | the device structures. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
diff --git a/doc/guides/rel_notes/supported_features.rst b/doc/guides/rel_notes/supported_features.rst
index 7efeff3..37e5416 100644
--- a/doc/guides/rel_notes/supported_features.rst
+++ b/doc/guides/rel_notes/supported_features.rst
@@ -61,7 +61,7 @@ Supported Features
* Virtualization (Xen)
- * Support for Intel® DPDK application running on Xen Domain0 without hugepages.
+ * Support for DPDK application running on Xen Domain0 without hugepages.
* Para-virtualization
@@ -70,7 +70,7 @@ Supported Features
Support userspace packet switching back-end example in host domain
* FreeBSD* 9.2 support for librte_pmd_e1000, librte_pmd_ixgbe and Virtual Function variants.
- Please refer to the *Intel® DPDK for FreeBSD\* Getting Started Guide*.
+ Please refer to the *DPDK for FreeBSD\* Getting Started Guide*.
Application support has been added for the following:
* multiprocess/symmetric_mp
@@ -87,7 +87,7 @@ Supported Features
* New VMXNET3 driver for the paravirtual device presented to a VM by the VMware* ESXi Hypervisor.
-* BETA: example support for basic Netmap applications on Intel® DPDK
+* BETA: example support for basic Netmap applications on DPDK
* Support for the wireless KASUMI algorithm in the dpdk_qat sample application
@@ -157,7 +157,7 @@ Supported Features
* Improved scalability for scheduling large numbers of timers using the rte_timer library
-* Support for building the Intel® DPDK as a shared library
+* Support for building the DPDK as a shared library
* Support for Intel® Ethernet Server Bypass Adapter X520-SR2
@@ -362,7 +362,7 @@ Supported Features
* Header files for common protocols (IP, SCTP, TCP, UDP)
-* Improved multi-process application support, allowing multiple co-operating Intel® DPDK
+* Improved multi-process application support, allowing multiple co-operating DPDK
processes to access the NIC port queues directly.
* CPU-specific compiler optimization
diff --git a/doc/guides/rel_notes/supported_os.rst b/doc/guides/rel_notes/supported_os.rst
index fb23dda..739cb2c 100644
--- a/doc/guides/rel_notes/supported_os.rst
+++ b/doc/guides/rel_notes/supported_os.rst
@@ -46,4 +46,4 @@ The following Linux* distributions were successfully used to generate or run the
* SUSE Enterprise Linux* 11 SP2
These distributions may need additional packages that are not installed by default, or a specific kernel.
-Refer to the *Intel® DPDK Getting Started Guide* for details.
+Refer to the *DPDK Getting Started Guide* for details.
diff --git a/doc/guides/rel_notes/updating_apps.rst b/doc/guides/rel_notes/updating_apps.rst
index ba8012d..034554d 100644
--- a/doc/guides/rel_notes/updating_apps.rst
+++ b/doc/guides/rel_notes/updating_apps.rst
@@ -1,11 +1,15 @@
Updating Applications from Previous Versions
============================================
-Although backward compatibility is being maintained across Intel® DPDK releases, code written for previous versions of the Intel® DPDK
-may require some code updates to benefit from performance and user experience enhancements provided in later Intel® DPDK releases.
+Although backward compatibility is being maintained across DPDK releases, code written for previous versions of the DPDK
+may require some code updates to benefit from performance and user experience enhancements provided in later DPDK releases.
-Intel® DPDK 1.6 to Intel® DPDK 1.7
-----------------------------------
+DPDK 1.7 to DPDK 1.8
+--------------------
+
+
+Intel® DPDK 1.6 to DPDK 1.7
+---------------------------
Note the following difference between 1.6 and 1.7:
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* Re: [dpdk-dev] [PATCH v4 6/8] doc: removed reference to Intel DPDK in Rel Notes
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 6/8] doc: removed reference to Intel DPDK in Rel Notes Pablo de Lara
@ 2014-12-18 15:22 ` Iremonger, Bernard
0 siblings, 0 replies; 49+ messages in thread
From: Iremonger, Bernard @ 2014-12-18 15:22 UTC (permalink / raw)
To: De Lara Guarch, Pablo, dev
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> Sent: Wednesday, December 17, 2014 4:48 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v4 6/8] doc: removed reference to Intel DPDK in Rel Notes
>
> From: Siobhan Butler <siobhan.a.butler@intel.com>
>
> Removed multiple references to Intel(R) DPDK where no longer
> relevant.
>
> Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
I have applied the patch to my tree next/dpdk-doc.
^ permalink raw reply [flat|nested] 49+ messages in thread
* [dpdk-dev] [PATCH v4 7/8] doc: updated resolved issues with old known issues
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
` (5 preceding siblings ...)
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 6/8] doc: removed reference to Intel DPDK in Rel Notes Pablo de Lara
@ 2014-12-17 16:47 ` Pablo de Lara
2014-12-18 15:24 ` Iremonger, Bernard
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 8/8] doc: updating the list of sample apps in rel notes Pablo de Lara
7 siblings, 1 reply; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:47 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Removed resolved issues from known issues section.
Added new resolved issues to resolved issues section.
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
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
------------------------------------------------------------------------------------
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* Re: [dpdk-dev] [PATCH v4 7/8] doc: updated resolved issues with old known issues
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 7/8] doc: updated resolved issues with old known issues Pablo de Lara
@ 2014-12-18 15:24 ` Iremonger, Bernard
0 siblings, 0 replies; 49+ messages in thread
From: Iremonger, Bernard @ 2014-12-18 15:24 UTC (permalink / raw)
To: De Lara Guarch, Pablo, dev
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> Sent: Wednesday, December 17, 2014 4:48 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v4 7/8] doc: updated resolved issues with old known issues
>
> From: Siobhan Butler <siobhan.a.butler@intel.com>
>
> Removed resolved issues from known issues section.
> Added new resolved issues to resolved issues section.
>
> Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
I have applied the patch to my tree next/dpdk-doc.
^ permalink raw reply [flat|nested] 49+ messages in thread
* [dpdk-dev] [PATCH v4 8/8] doc: updating the list of sample apps in rel notes
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
` (6 preceding siblings ...)
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 7/8] doc: updated resolved issues with old known issues Pablo de Lara
@ 2014-12-17 16:47 ` Pablo de Lara
2014-12-18 15:25 ` Iremonger, Bernard
7 siblings, 1 reply; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:47 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Added new and existing names of sample apps to list of
sample apps in release notes.
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/rel_description.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/rel_notes/rel_description.rst b/doc/guides/rel_notes/rel_description.rst
index 8da53c4..49f32b9 100644
--- a/doc/guides/rel_notes/rel_description.rst
+++ b/doc/guides/rel_notes/rel_description.rst
@@ -113,10 +113,14 @@ The following is a list of DPDK documents in the suggested reading order:
* L3 Forwarding
+ * L3 Forwarding with Access Control
+
* L3 Forwarding with Power Management
* L3 Forwarding in a Virtualized Environment
+ * Link Status Interrupt
+
* Load Balancing
* Multi-process
@@ -143,6 +147,8 @@ The following is a list of DPDK documents in the suggested reading order:
* VM Power Management
+ * Distributor
+
In addition, there are some other applications that are built when the libraries are created.
The source for these applications is in the DPDK/app directory and are called:
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* Re: [dpdk-dev] [PATCH v4 8/8] doc: updating the list of sample apps in rel notes
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 8/8] doc: updating the list of sample apps in rel notes Pablo de Lara
@ 2014-12-18 15:25 ` Iremonger, Bernard
0 siblings, 0 replies; 49+ messages in thread
From: Iremonger, Bernard @ 2014-12-18 15:25 UTC (permalink / raw)
To: De Lara Guarch, Pablo, dev
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> Sent: Wednesday, December 17, 2014 4:48 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v4 8/8] doc: updating the list of sample apps in rel notes
>
> From: Siobhan Butler <siobhan.a.butler@intel.com>
>
> Added new and existing names of sample apps to list of sample apps in release notes.
>
> Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
I have applied the patch to my tree next/dpdk-doc.
^ permalink raw reply [flat|nested] 49+ messages in thread
* [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes
2014-12-16 14:48 ` [dpdk-dev] [PATCH v3 0/8] doc: patch set to update release notes Siobhan Butler
` (8 preceding siblings ...)
2014-12-17 16:47 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
@ 2014-12-17 16:58 ` Pablo de Lara
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 1/8] doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes Pablo de Lara
` (7 more replies)
9 siblings, 8 replies; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:58 UTC (permalink / raw)
To: dev
New Features section:
- Removed 1.7 New Features
- Added 1.8.0 New Features
Supported Features section:
- Added 1.7 features to Supported Features
Known Issues:
- Added devices to Known issue "Not all varients of supported NIC types have been used in testing"
- Removed known issue 6.29 "Double VLAN not working on 40GbE Ethnet Controller" as resolved
Resolved issues:
- Added known issue 6.29 to resolved issues
Removed references across all sections to Intel DPDK where no longer relevant.
Added new sample apps to sample apps list in release notes.
Moved issues newly resolved from known issues to resolved issues.
Removed Intel Licensing Appendix A as no longer relevant.
Siobhan Butler (8):
doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes
doc: added new features to release notes
doc: added to known issue 6.10 and removed fixed issue 6.29 from
rel_notes
doc: moved known issue 6.29 to resolved issues in rel notes
doc: remove appendix a from release notes
doc: removed reference to Intel DPDK in Rel Notes
doc: updated resolved issues with old known issues
doc: updating the list of sample apps in rel notes
doc/guides/rel_notes/appendices.rst | 324 ----------------------------
doc/guides/rel_notes/faq.rst | 14 +-
doc/guides/rel_notes/index.rst | 44 ----
doc/guides/rel_notes/known_issues.rst | 281 ++----------------------
doc/guides/rel_notes/new_features.rst | 25 ++-
doc/guides/rel_notes/rel_description.rst | 42 ++--
doc/guides/rel_notes/resolved_issues.rst | 271 ++++++++++++++++++++---
doc/guides/rel_notes/supported_features.rst | 32 ++-
doc/guides/rel_notes/supported_os.rst | 2 +-
doc/guides/rel_notes/updating_apps.rst | 12 +-
10 files changed, 331 insertions(+), 716 deletions(-)
delete mode 100644 doc/guides/rel_notes/appendices.rst
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 1/8] doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
@ 2014-12-17 16:58 ` Pablo de Lara
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 2/8] doc: added new features to release notes Pablo de Lara
` (6 subsequent siblings)
7 siblings, 0 replies; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:58 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/new_features.rst | 17 -----------------
doc/guides/rel_notes/supported_features.rst | 22 ++++++++++++++++++++++
2 files changed, 22 insertions(+), 17 deletions(-)
diff --git a/doc/guides/rel_notes/new_features.rst b/doc/guides/rel_notes/new_features.rst
index 568d0c9..a93aa3c 100644
--- a/doc/guides/rel_notes/new_features.rst
+++ b/doc/guides/rel_notes/new_features.rst
@@ -31,22 +31,5 @@
New Features
============
-* Packet Distributor library for dynamic, single-packet at a time, load balancing
-
-* IP fragmentation and reassembly library
-
-* Support for IPv6 in IP fragmentation and reassembly sample applications
-
-* Support for VFIO for mapping BARs and setting up interrupts
-
-* Link Bonding PMD Library supporting round-robin, active backup, balance(layer 2, layer 2+3, and layer 3+4) and broadcast bonding modes
-
-* Support zero copy mode RX/TX in user space vhost sample
-
-* Support multiple queues in virtio-net PMD
-
-* Support for Intel® 40GbE Controllers
-
-* Support NIC filters in addition to flow director for Intel® 1GbE and 10GbE Controllers
For further features supported in this release, see Chapter 3 Supported Features.
diff --git a/doc/guides/rel_notes/supported_features.rst b/doc/guides/rel_notes/supported_features.rst
index c51eb26..7efeff3 100644
--- a/doc/guides/rel_notes/supported_features.rst
+++ b/doc/guides/rel_notes/supported_features.rst
@@ -31,6 +31,28 @@
Supported Features
==================
+* Packet Distributor library for dynamic, single-packet at a time, load balancing
+
+* IP fragmentation and reassembly library
+
+* Support for IPv6 in IP fragmentation and reassembly sample applications
+
+* Support for VFIO for mapping BARs and setting up interrupts
+
+* Link Bonding PMD Library supporting round-robin, active backup, balance(layer 2, layer 2+3, and layer 3+4) and broadcast bonding modes
+
+* Support zero copy mode RX/TX in user space vhost sample
+
+* Support multiple queues in virtio-net PMD
+
+* Support for Intel 40GbE Controllers:
+
+ * Intel(R) XL710 40 Gigabit Ethernet Controller
+
+ * Intel(R) X710 40 Gigabit Ethernet Controller
+
+* Support NIC filters in addition to flow director for Intel� 1GbE and 10GbE Controllers
+
* Virtualization (KVM)
* Userspace vhost switch:
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 2/8] doc: added new features to release notes
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 1/8] doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes Pablo de Lara
@ 2014-12-17 16:58 ` Pablo de Lara
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 3/8] doc: added to known issue 6.10 and removed fixed issue 6.29 from rel_notes Pablo de Lara
` (5 subsequent siblings)
7 siblings, 0 replies; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:58 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/new_features.rst | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/doc/guides/rel_notes/new_features.rst b/doc/guides/rel_notes/new_features.rst
index a93aa3c..00895ce 100644
--- a/doc/guides/rel_notes/new_features.rst
+++ b/doc/guides/rel_notes/new_features.rst
@@ -30,6 +30,30 @@
New Features
============
+* Link Bonding
+ * Support for 802.3ad link aggregation (mode 4) and transmit load balancing (mode 5) to the link bonding library.
+
+ * Support for registration of link status change callbacks with link bonding devices.
+
+ * Support for slaves devices which do not support link status change interrupts in the link bonding library via a link status polling mechanism.
+
+* Poll Mode Driver - 40 GbE Controllers (librte_pmd_i40e)
+
+ * Support for Flow Director
+
+ * Support for ethertype filter
+
+ * Support RSS in VF
+
+ * Support configuring redirection table with different size from 1GbE and 10 GbE
+
+ - 128/512 entries of 40GbE PF
+
+ - 64 entries of 40GbE VF
+
+ * Support configuring hash functions
+
+* Packet Distributor Sample Application
For further features supported in this release, see Chapter 3 Supported Features.
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 3/8] doc: added to known issue 6.10 and removed fixed issue 6.29 from rel_notes
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 1/8] doc: moved 1.7 new features to supported features for 1.8 in Rel_Notes Pablo de Lara
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 2/8] doc: added new features to release notes Pablo de Lara
@ 2014-12-17 16:58 ` Pablo de Lara
2014-12-18 15:19 ` Iremonger, Bernard
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 4/8] doc: moved known issue 6.29 to resolved issues in rel notes Pablo de Lara
` (4 subsequent siblings)
7 siblings, 1 reply; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:58 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/known_issues.rst | 36 ++++++-----------------------------
1 file changed, 6 insertions(+), 30 deletions(-)
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index d26dcfa..1cfc977 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -338,6 +338,12 @@ Not all variants of supported NIC types have been used in testing
| | |
| | The NIC device identifiers used during testing: |
| | |
+| | * Intel(R) Ethernet Controller XL710 for 40GbE QSFP+ [8086:1584] |
+| | |
+| | * Intel(R) Ethernet Controller XL710 for 40GbE QSFP+ [8086:1583] |
+| | |
+| | * Intel(R) Ethernet Controller X710 for 10GbE SFP+ [8086:1572] |
+| | |
| | * Intel® 82576 Gigabit Ethernet Controller [8086:10c9] |
| | |
| | * Intel® 82576 Quad Copper Gigabit Ethernet Controller [8086:10e8] |
@@ -940,36 +946,6 @@ Ethertype filter could receive other packets (non-assigned) in Niantic
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-Double VLAN does not work on Intel® 40G ethernet controller
------------------------------------------------------------
-
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Title | Double VLAN does not work on Intel® 40G ethernet controller |
-| | |
-+================================+======================================================================================+
-| Reference # | IXA00386480 |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | On Intel® 40G Ethernet Controller: |
-| | |
-| | Double VLAN does not work. This was confirmed a firmware issue which will be fixed |
-| | in later versions of firmware. |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | After setting double vlan to be enabled on a port, no packets can be transmitted out |
-| | on that port. |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Resolution/ Workaround | None |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Affected Environment/ Platform | All |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-| Driver/Module | Poll Mode Driver (PMD) |
-| | |
-+--------------------------------+--------------------------------------------------------------------------------------+
-
Cannot set link speed on Intel® 40G ethernet controller
-------------------------------------------------------
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 4/8] doc: moved known issue 6.29 to resolved issues in rel notes
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
` (2 preceding siblings ...)
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 3/8] doc: added to known issue 6.10 and removed fixed issue 6.29 from rel_notes Pablo de Lara
@ 2014-12-17 16:58 ` Pablo de Lara
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 5/8] doc: remove appendix a from release notes Pablo de Lara
` (3 subsequent siblings)
7 siblings, 0 replies; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:58 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/resolved_issues.rst | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/doc/guides/rel_notes/resolved_issues.rst b/doc/guides/rel_notes/resolved_issues.rst
index f9ddb7f..66afc25 100644
--- a/doc/guides/rel_notes/resolved_issues.rst
+++ b/doc/guides/rel_notes/resolved_issues.rst
@@ -1192,3 +1192,33 @@ Packet reception issues when virtualization is enabled
| Driver/Module | Poll mode drivers |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
+
+
+
+Double VLAN does not work on Intel� 40GbE ethernet contoller
+------------------------------------------------------------
+
++---------------------------------+---------------------------------------------------------------------------------------+
+| Title | Double VLAN does not work on Intel� 40GbE ethernet controller |
+| | |
++=================================+=======================================================================================+
+| Reference # | IXA00369908 |
+| | |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Description | On Intel(R) 40 GbE ethernet controller double VLAN does not work. |
+| | This was confirmed as a Firmware issue which will be fixed in later versions of |
+| | firmware. |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Implication | After setting double vlan to be enabled on a port, no packets can be transmitted out |
+| | on that port. |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Resolution/Workaround | Resolved in latest release with firmware upgrade. |
+| | |
+| | |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Affected Environment/Platform | All |
+| | |
++---------------------------------+---------------------------------------------------------------------------------------+
+| Driver/Module | Poll mode drivers |
+| | |
++---------------------------------+---------------------------------------------------------------------------------------+
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 5/8] doc: remove appendix a from release notes
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
` (3 preceding siblings ...)
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 4/8] doc: moved known issue 6.29 to resolved issues in rel notes Pablo de Lara
@ 2014-12-17 16:58 ` Pablo de Lara
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 6/8] doc: removed reference to Intel DPDK in Rel Notes Pablo de Lara
` (2 subsequent siblings)
7 siblings, 0 replies; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:58 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Removing Appendix A from Release Notes as Intel Licensing information is
no longer relevant in this document.
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/appendices.rst | 324 ------------------------------------
doc/guides/rel_notes/index.rst | 44 -----
2 files changed, 368 deletions(-)
delete mode 100644 doc/guides/rel_notes/appendices.rst
diff --git a/doc/guides/rel_notes/appendices.rst b/doc/guides/rel_notes/appendices.rst
deleted file mode 100644
index 6dec2e1..0000000
--- a/doc/guides/rel_notes/appendices.rst
+++ /dev/null
@@ -1,324 +0,0 @@
-.. BSD LICENSE
- Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
- All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
-
- * Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
- * Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in
- the documentation and/or other materials provided with the
- distribution.
- * Neither the name of Intel Corporation nor the names of its
- contributors may be used to endorse or promote products derived
- from this software without specific prior written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-Appendix A Intel® DPDK License Overview
-=========================================
-
-
-The following describes the various licenses used by the Intel® Data Plane Development Kit (Intel® DPDK).
-The purpose of the Intel® DPDK is to prove the abilities of the Intel® architecture processors and to provide users with a strong set of examples, libraries and proof points.
-By placing the majority of this software under the BSD License, users may choose to use the Intel® as is, parts of it, or just the ideas for their programs.
-All code may be modified by the user to suit their project needs and requirements.
-
-.. note::
-
- The license in each source file takes precedence over this document, and should be used as the definitive license for that file.
- All users should seek their legal team's guidance with respect to the licensing used by the Intel® DPDK.
-
-
-
-The following table lists those files (or libraries) that are not under a BSD License. In some cases, these files are part of the standard Intel® DPDK release package,
-and in other cases may be a separate package that requires a separate download to be added to the Intel® DPDK. This document spells out those cases where possible.
-
-The sections following the table provide the various licenses used. Please note that copyright notices may change overtime.
-It is the responsibility of all users to understand these licenses and seek their legal team's guidance.
-
-The use of the GPLv2 License is confined to files in kernel loadable modules.
-
-The use of the Dual BSD/LGPLv2 License and Dual BSD/GPL License allows use with either free/open source software or with proprietary software in userspace.
-
-
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| File | Description | License |
-| | | |
-+===================================================+======================================================================================================================+======================================+
-| igb_uio.c | **1st Released** | GPLv2 License Information |
-| | : 1.0 | |
-| | | |
-| | **Location** | |
-| | : | |
-| | DPDK/lib/librte_eal/linuxapp/igb_uio/ | |
-| | | |
-| | **Description** | |
-| | : This file is used for a kernel loadable module which is responsible for unbinding NICs from the Linux kernel | |
-| | and binding them to the Intel® DPDK | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| kni_dev.h kni_ethtool.c kni_misc.c kni_net.c | **1st Released** | GPLv2 License Information |
-| | : 1.3 | |
-| | | |
-| | **Location** | |
-| | : DPDK/lib/librte_eal/linuxapp/kni/ | |
-| | | |
-| | **Description** | |
-| | : The KNI kernel loadable module is a standard net driver which allows Intel DPDK Linux userspace applications | |
-| | to exchange packets/data with the Linux kernel. | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| rte_kni_common.h | **1st Released** | Dual BSD/LGPLv2 License Information |
-| | : 1.3 | |
-| | | |
-| | **Location** | |
-| | : DPDK/lib/librte_eal/linuxapp/eal/include/exec-env/ | |
-| | | |
-| | **Description** | |
-| | : The KNI header files is utilized by both the Intel DPDK userspace application and the KNI kernel loadable module | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| All files under this directory are for the | **1st Released** | GPLv2 License Information |
-| ethtool functionality. | : 1.3 | |
-| | | |
-| | **Location** | |
-| | : DPDK/lib/librte_eal/linuxapp/kni/ethtool | |
-| | | |
-| | **Description** | |
-| | : The igb and ixgbe drivers for the Ethtool function available with the KNI kernel loadable. | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-| rte_pci_dev_ids.h | **1st Released** | Dual BSD/GPL License Information |
-| | : 1.3 | |
-| | | |
-| | **Location** | |
-| | : DPDK/lib/librte_eal/common/include | |
-| | | |
-| | **Description** | |
-| | : Contains the PCI device ids for all devices. | |
-| | | |
-+---------------------------------------------------+----------------------------------------------------------------------------------------------------------------------+--------------------------------------+
-
-Added rte_dom0_mm.h file for Dual BSD/LGPLv2 License information:
-
-rte_dom0_mm.h 1st Released 1.6.0
-
-Location: DPDK/lib/librte_eal/eal/include/exec-env/
-
-Description: The Dom0 header file is utilized by both the Intel® DPDK userspace application and the Dom0 kernel loadable module
-
-Added dom0_mm_misc.h and dom0_mm_misc.c file for Dual BSD/GPLv2 License Information:
-
-dom0_mm_dev.h 1st Released 1.6.0
-
-dom0_mm_dev.c Location: DPDK/lib/librte_eal/linuxapp/xen_dom0
-
-Description: The Dom0 memory management kernel loadable module is a misc device driver which is used to facilitate allocating and mapping via an **IOCTL** (allocation) and **MMAP** (mapping).
-
-
-A.1 BSD License
----------------
-
-.. code-block:: c
-
- /*-
- * BSD LICENSE
- *
- * Copyright(c) 2010-2012 Intel Corporation. All rights reserved.
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * * Redistributions of source code must retain the above copyright
- * notice, this list of conditions and the following disclaimer.
- * * Redistributions in binary form must reproduce the above copyright
- * notice, this list of conditions and the following disclaimer in
- * the documentation and/or other materials provided with the
- * distribution.
- * * Neither the name of Intel Corporation nor the names of its
- * contributors may be used to endorse or promote products derived
- * from this software without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- *
- */
-
-A.2 GPLv2 License Information
------------------------------
-
-.. code-block:: c
-
- /*-
- *
- * Copyright (c) 2010-2012, Intel Corporation
- *
- * This program is free software; you can redistribute it and/or
- * modify it under the terms of the GNU General Public License
- * as published by the Free Software Foundation; either version 2
- * of the License, or (at your option) any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
- *
-..
-
- \* GNU GPL V2: `http://www.gnu.org/licenses/old-licenses/gpl-2.0.html <http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>`_
-
-.. code-block:: c
-
- *
- */
-
-A.3 Dual BSD/LGPLv2 License Information
----------------------------------------
-
-.. code-block:: c
-
- /*
- This file is provided under a dual BSD/LGPLv2 license. When using
- or redistributing this file, you may do so under either license.
-
- GNU LESSER GENERAL PUBLIC LICENSE
-
- Copyright(c) 2007,2008,2009 Intel Corporation. All rights reserved.
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of version 2.1 of the GNU Lesser General Public License
- as published by the Free Software Foundation.
-
- This program is distributed in the hope that it will be useful, but WITHOUT ANY
- WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- PARTICULAR PURPOSE. See the GNU
- Lesser General Public License for more details.
-
- You should have received a copy of the GNU Lesser General Public License along with
- this program; if not, write to the Free Software
- Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
-
-
- Contact Information: Intel Corporation
-
- BSD LICENSE
-
- Copyright(c) 2010-2012 Intel Corporation.All rights reserved. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without modification, are
- permitted provided that the following conditions are met:
-
- Redistributions of source code must retain the above copyright notice, this list of
- conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list
- of conditions and the following disclaimer in the documentation and/or other
- materials provided with the distribution.
- Neither the name of Intel Corporation nor the names of its contributors may be used
- to endorse or promote products derived from this software without specific prior
- written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
- EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
- SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
- TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
- BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
- CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
- ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
- DAMAGE.
- */
-
-
-A.4 Dual BSD/GPL License Information
-------------------------------------
-
-.. code-block:: c
-
- /*-
- * This file is provided under a dual BSD/GPLv2 license. When using or
- * redistributing this file, you may do so under either license.
- *
- * GPL LICENSE SUMMARY
- *
- * Copyright(c) 2010-2012 Intel Corporation. All rights reserved.
- *
- * This program is free software; you can redistribute it and/or modify
- * it under the terms of version 2 of the GNU General Public License as
- * published by the Free Software Foundation.
- *
- * This program is distributed in the hope that it will be useful, but
- * WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
- * General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
- * The full GNU General Public License is included in this distribution
- * in the file called LICENSE.GPL.
- *
- * Contact Information:
- * Intel Corporation
- *
- * BSD LICENSE
- *
- * Copyright(c) 2010-2012 Intel Corporation. All rights reserved.
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * * Redistributions of source code must retain the above copyright
- * notice, this list of conditions and the following disclaimer.
- * * Redistributions in binary form must reproduce the above copyright
- * notice, this list of conditions and the following disclaimer in
- * the documentation and/or other materials provided with the
- * distribution.
- * * Neither the name of Intel Corporation nor the names of its
- * contributors may be used to endorse or promote products derived
- * from this software without specific prior written permission.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- *
- */
diff --git a/doc/guides/rel_notes/index.rst b/doc/guides/rel_notes/index.rst
index e9a3d21..69e59d4 100644
--- a/doc/guides/rel_notes/index.rst
+++ b/doc/guides/rel_notes/index.rst
@@ -35,49 +35,6 @@ Package Version: 1.7
|today|
-INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS.
-NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT.
-EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY,
-RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT,
-COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
-
-A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death.
-SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES,
-AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY,
-ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN,
-MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS.
-
-Intel may make changes to specifications and product descriptions at any time, without notice.
-Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined".
-Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.
-The information here is subject to change without notice.
-Do not finalize a design with this information.
-
-The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications.
-Current characterized errata are available on request.
-
-Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
-
-Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling
-1-800-548-4725, or go to:
-`http://www.intel.com/design/literature.htm <http://www.intel.com/design/literature.htm>`_
-
-Any software source code reprinted in this document is furnished for informational purposes only and may only be used or copied and no license, express or implied, by estoppel or otherwise,
-to any of the reprinted source code is granted by this document.
-
-Code Names are only for use by Intel to identify products, platforms, programs, services, etc. ("products") in development by
-Intel that have not been made commercially available to the public, i.e., announced, launched or shipped. They are never to be used as "commercial" names for products.
-Also, they are not intended to function as trademarks.
-
-See Appendix A for an overview of the applicable software licenses.
-
-Intel, the Intel logo, Intel Core and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
-
-\*Other names and brands may be claimed as the property of others.
-
-Copyright © 2012-2014 , Intel Corporation. All rights reserved.
-
-
Contents
.. toctree::
@@ -92,4 +49,3 @@ Contents
known_issues
resolved_issues
faq
- appendices
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 6/8] doc: removed reference to Intel DPDK in Rel Notes
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
` (4 preceding siblings ...)
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 5/8] doc: remove appendix a from release notes Pablo de Lara
@ 2014-12-17 16:58 ` Pablo de Lara
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 7/8] doc: updated resolved issues with old known issues Pablo de Lara
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 8/8] doc: updating the list of sample apps in rel notes Pablo de Lara
7 siblings, 0 replies; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:58 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Removed multiple references to Intel(R) DPDK where no longer
relevant.
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/faq.rst | 14 +++---
doc/guides/rel_notes/known_issues.rst | 30 ++++++-------
doc/guides/rel_notes/rel_description.rst | 36 ++++++---------
doc/guides/rel_notes/resolved_issues.rst | 70 ++++++++++++++---------------
doc/guides/rel_notes/supported_features.rst | 10 ++---
doc/guides/rel_notes/supported_os.rst | 2 +-
doc/guides/rel_notes/updating_apps.rst | 12 +++--
7 files changed, 85 insertions(+), 89 deletions(-)
diff --git a/doc/guides/rel_notes/faq.rst b/doc/guides/rel_notes/faq.rst
index dfc34e6..054db10 100644
--- a/doc/guides/rel_notes/faq.rst
+++ b/doc/guides/rel_notes/faq.rst
@@ -36,7 +36,7 @@ When running the test application, I get “EAL: map_all_hugepages(): open faile
This is most likely due to the test application not being run with sudo to promote the user to a superuser.
Alternatively, applications can also be run as regular user.
-For more information, please refer to *Intel® DPDK Getting Started Guide*.
+For more information, please refer to *DPDK Getting Started Guide*.
If I want to change the number of TLB Hugepages allocated, how do I remove the original pages allocated?
--------------------------------------------------------------------------------------------------------
@@ -49,7 +49,7 @@ If you look in the directory, you will see n number of 2M pages files. If you sp
These are then placed in memory segments to get contiguous memory.
If you need to change the number of pages, it is easier to first remove the pages. The tools/setup.sh script provides an option to do this.
-See the “Quick Start Setup Script” section in the *Intel® DPDK Getting Started Guide* for more information.
+See the “Quick Start Setup Script” section in the *DPDK Getting Started Guide* for more information.
If I execute “l2fwd -c f -m 64 –n 3 -- -p 3”, I get the following output, indicating that there are no socket 0 hugepages to allocate the mbuf and ring structures to?
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -59,14 +59,14 @@ I have set up a total of 1024 Hugepages (that is, allocated 512 2M pages to each
The -m command line parameter does not guarantee that huge pages will be reserved on specific sockets. Therefore, allocated huge pages may not be on socket 0.
To request memory to be reserved on a specific socket, please use the --socket-mem command-line parameter instead of -m.
-I am running a 32-bit Intel® DPDK application on a NUMA system, and sometimes the application initializes fine but cannot allocate memory. Why is that happening?
+I am running a 32-bit DPDK application on a NUMA system, and sometimes the application initializes fine but cannot allocate memory. Why is that happening?
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
32-bit applications have limitations in terms of how much virtual memory is available, hence the number of hugepages they are able to allocate is also limited (1 GB per page size).
If your system has a lot (>1 GB per page size) of hugepage memory, not all of it will be allocated.
Due to hugepages typically being allocated on a local NUMA node, the hugepages allocation the application gets during the initialization depends on which
NUMA node it is running on (the EAL does not affinitize cores until much later in the initialization process).
-Sometimes, the Linux OS runs the Intel® DPDK application on a core that is located on a different NUMA node from Intel® DPDK master core and
+Sometimes, the Linux OS runs the DPDK application on a core that is located on a different NUMA node from DPDK master core and
therefore all the hugepages are allocated on the wrong socket.
To avoid this scenario, either lower the amount of hugepage memory available to 1 GB per page size (or less), or run the application with taskset
@@ -102,7 +102,7 @@ Traditionally, there is a trade-off between throughput and latency. An applicati
but the end-to-end latency of an average packet typically increases as a result.
Similarly, the application can be tuned to have, on average, a low end-to-end latency at the cost of lower throughput.
-To achieve higher throughput, the Intel® DPDK attempts to aggregate the cost of processing each packet individually by processing packets in bursts.
+To achieve higher throughput, the DPDK attempts to aggregate the cost of processing each packet individually by processing packets in bursts.
Using the testpmd application as an example, the “burst” size can be set on the command line to a value of 16 (also the default value).
This allows the application to request 16 packets at a time from the PMD.
The testpmd application then immediately attempts to transmit all the packets that were received, in this case, all 16 packets.
@@ -144,11 +144,11 @@ For best performance with NUMA disabled, only one socket should be populated.
I am getting errors about not being able to open files. Why?
------------------------------------------------------------
-As the Intel® DPDK operates, it opens a lot of files, which can result in reaching the open files limits, which is set using the ulimit command or in the limits.conf file.
+As the DPDK operates, it opens a lot of files, which can result in reaching the open files limits, which is set using the ulimit command or in the limits.conf file.
This is especially true when using a large number (>512) of 2 MB huge pages. Please increase the open file limit if your application is not able to open files.
This can be done either by issuing a ulimit command or editing the limits.conf file. Please consult Linux* manpages for usage information.
-Does my kernel require patching to run the Intel® DPDK?
+Does my kernel require patching to run the DPDK?
-------------------------------------------------------
Any kernel greater than version 2.6.33 can be used without any patches applied. The following kernels may require patches to provide hugepage support:
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 1cfc977..0107f9d 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -31,7 +31,7 @@
Known Issues and Limitations
============================
-This section describes known issues with the Intel® DPDK software, Release 1.6.0.
+This section describes known issues with the DPDK software, Release 1.8.0.
Pause Frame Forwarding does not work properly on igb
----------------------------------------------------
@@ -112,13 +112,13 @@ Vhost-xen cannot detect Domain U application exit on Xen version 4.0.1
| Reference # | IXA00168947 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | When using Intel® DPDK applications on Xen 4.0.1, e.g. TestPMD Sample Application, |
+| 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 |
+| | 4.0.1 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Resolution | |
@@ -154,7 +154,7 @@ Virtio incorrect header length used if MSI-X is disabled by kernel driver
| | specification and resolves to the VIRTIO_NET_F_MAC feature instead. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | The Intel® DPDK kernel driver will enable MSI-X by default, |
+| 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”. |
@@ -425,13 +425,13 @@ Unstable system performance across application executions with 2MB pages
| Reference # | IXA00372346 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | The performance of an Intel® DPDK application may vary across executions of an |
+| 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 Intel® DPDK applications is encountered.|
+| 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. |
@@ -536,7 +536,7 @@ PMD does not work with --no-huge EAL command line parameter
| Reference # | IXA00373461 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | Currently, the Intel® DPDK does not store any information about memory allocated by |
+| Description | Currently, the DPDK does not store any information about memory allocated by |
| | malloc() (for example, NUMA node, physical address), hence PMD drivers do not work |
| | when the --no-huge command line parameter is supplied to EAL. |
| | |
@@ -547,7 +547,7 @@ PMD does not work with --no-huge EAL command line parameter
| Resolution/ Workaround | Use huge page memory or use VFIO to map devices. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Affected Environment/ Platform | Systems running the Intel® DPDK on Linux |
+| Affected Environment/ Platform | Systems running the DPDK on Linux |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Driver/Module | Poll Mode Driver (PMD) |
@@ -701,24 +701,24 @@ Discrepancies between statistics reported by different NICs
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-Error reported opening files on Intel® DPDK initialization
-----------------------------------------------------------
+Error reported opening files on DPDK initialization
+---------------------------------------------------
+--------------------------------+--------------------------------------------------------------------------------------+
-| Title | Error reported opening files on Intel® DPDK initialization |
+| Title | Error reported opening files on DPDK initialization |
| | |
+================================+======================================================================================+
| Reference # | 91 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | On Intel® DPDK application startup, errors may be reported when opening files as |
+| Description | On DPDK application startup, errors may be reported when opening files as |
| | part of the initialization process. This occurs if a large number, for example, 500 |
| | or more, or if hugepages are used, due to the per-process limit on the number of |
| | open files. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | The Intel® DPDK application may fail to run. |
+| Implication | The DPDK application may fail to run. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Resolution/ Workaround | If using 2 MB hugepages, consider switching to a fewer number of 1 GB pages. |
@@ -890,11 +890,11 @@ GCC might generate Intel® AVX instructions forprocessors without Intel® AVX su
| Reference # | IXA00382439 |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Description | When compiling Intel® DPDK (and any Intel® DPDK app), gcc may generate Intel® AVX |
+| Description | When compiling Intel® DPDK (and any DPDK app), gcc may generate Intel® AVX |
| | instructions, even when the processor does not support Intel® AVX. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | Any Intel® DPDK app might crash while starting up. |
+| Implication | Any DPDK app might crash while starting up. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Resolution/ Workaround | Either compile using icc or set EXTRA_CFLAGS=’-O3’ prior to compilation. |
diff --git a/doc/guides/rel_notes/rel_description.rst b/doc/guides/rel_notes/rel_description.rst
index d159b3c..8da53c4 100644
--- a/doc/guides/rel_notes/rel_description.rst
+++ b/doc/guides/rel_notes/rel_description.rst
@@ -32,22 +32,14 @@ Description of Release
======================
These release notes cover the new features,
-fixed bugs and known issues for Intel® Data Plane Development Kit (Intel® DPDK) release version 1.7.0.
+fixed bugs and known issues for Data Plane Development Kit (DPDK) release version 1.7.0.
-For instructions on compiling and running the release, see the *Intel® DPDK Getting Started Guide*.
+For instructions on compiling and running the release, see the *DPDK Getting Started Guide*.
-Important Note
---------------
+Using DPDK Upgrade Patches
+--------------------------
-All Intel® DPDK questions and technical problems including those regarding the Ethernet* Controllers for the Poll Mode Driver should be reported through the Intel® Premier Support site
-`http://premier.intel.com/premier <http://premier.intel.com/premier>`_
-or access your IBL account and click the **Intel® Premier Support** link to enter issues under the Product Name “Data Plane Development Kit (DPDK)”,
-which are then routed to our support team.
-
-Using Intel® DPDK Upgrade Patches
----------------------------------
-
-For minor updates to the main Intel® DPDK releases, the software may be made available both as a new full package and as a patch file to be applied to the previously released package.
+For minor updates to the main DPDK releases, the software may be made available both as a new full package and as a patch file to be applied to the previously released package.
In the latter case, the following commands should be used to apply the patch on top of the already-installed package for the previous release:
.. code-block:: console
@@ -55,7 +47,7 @@ In the latter case, the following commands should be used to apply the patch on
# cd $RTE_SDK
# patch –p1 < /path/to/patch/file
-Once the patch has been applied cleanly, the Intel® DPDK can be recompiled and used as before (described in the *Intel® DPDK Getting Started Guide*).
+Once the patch has been applied cleanly, the DPDK can be recompiled and used as before (described in the *DPDK Getting Started Guide*).
.. note::
@@ -65,25 +57,25 @@ Once the patch has been applied cleanly, the Intel® DPDK can be recompiled and
Documentation Roadmap
---------------------
-The following is a list of Intel® DPDK documents in the suggested reading order:
+The following is a list of DPDK documents in the suggested reading order:
* **Release Notes**
(this document): Provides release-specific information, including supported features, limitations, fixed issues, known issues and so on.
Also, provides the answers to frequently asked questions in FAQ format.
* **Getting Started Guide**
- : Describes how to install and configure the Intel® DPDK software; designed to get users up and running quickly with the software.
+ : Describes how to install and configure the DPDK software; designed to get users up and running quickly with the software.
* **FreeBSD* Getting Started Guide**
- : A document describing the use of the Intel® DPDK with FreeBSD* has been added in Intel® DPDK Release 1.6.0.
- Refer to this guide for installation and configuration instructions to get started using the Intel® DPDK with FreeBSD*.
+ : A document describing the use of the DPDK with FreeBSD* has been added in DPDK Release 1.6.0.
+ Refer to this guide for installation and configuration instructions to get started using the DPDK with FreeBSD*.
* **Programmer's Guide**
: Describes:
* The software architecture and how to use it (through examples), specifically in a Linux* application (linuxapp) environment
- * The content of the Intel® DPDK, the build system (including the commands that can be used in the root Intel® DPDK Makefile to build the development kit and an application)
+ * The content of the DPDK, the build system (including the commands that can be used in the root DPDK Makefile to build the development kit and an application)
and guidelines for porting an application
* Optimizations used in the software and those that should be considered for new development
@@ -91,7 +83,7 @@ The following is a list of Intel® DPDK documents in the suggested reading order
A glossary of terms is also provided.
* **API Reference**
- : Provides detailed information about Intel® DPDK functions, data structures and other programming constructs.
+ : Provides detailed information about DPDK functions, data structures and other programming constructs.
* **Sample Applications User Guide**
: Describes a set of sample applications. Each chapter describes a sample application that showcases specific functionality and provides instructions on how to compile,
@@ -160,11 +152,11 @@ The following is a list of Intel® DPDK documents in the suggested reading order
Once the libraries are created, they can be found in the build/app directory.
- * The test application provides a variety of specific tests for the various functions in the Intel® DPDK.
+ * The test application provides a variety of specific tests for the various functions in the DPDK.
* The testpmd application provides a number of different packet throughput tests and examples of features such as
how to use the Flow Director found in the Intel® 82599 10 Gigabit Ethernet Controller.
- The testpmd application is documented in the *Intel® DPDK Testpmd Application Note* (525362).
+ The testpmd application is documented in the *DPDK Testpmd Application Note* (525362).
The test application is not currently documented.
However, you should be able to run and use test application with the command line help that is provided in the application.
diff --git a/doc/guides/rel_notes/resolved_issues.rst b/doc/guides/rel_notes/resolved_issues.rst
index 66afc25..16e1026 100644
--- a/doc/guides/rel_notes/resolved_issues.rst
+++ b/doc/guides/rel_notes/resolved_issues.rst
@@ -200,7 +200,7 @@ Device initialization failure with Intel® Ethernet Server Adapter X520-T2
| Reference # | 55 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Description | If this device is bound to the Linux kernel IXGBE driver when the Intel® DPDK is |
+| Description | If this device is bound to the Linux kernel IXGBE driver when the DPDK is |
| | initialized, DPDK is initialized, the device initialization fails with error code -17 |
| | “IXGBE_ERR_PHY_ADDR_INVALID”. |
| | |
@@ -208,7 +208,7 @@ Device initialization failure with Intel® Ethernet Server Adapter X520-T2
| Implication | The device is not initialized and cannot be used by an application. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution/Workaround | Introduced a small delay in device initialization to allow Intel® DPDK to always find |
+| Resolution/Workaround | Introduced a small delay in device initialization to allow DPDK to always find |
| | the device. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -219,11 +219,11 @@ Device initialization failure with Intel® Ethernet Server Adapter X520-T2
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-Intel® DPDK kernel module is incompatible with Linux kernel version 3.3
------------------------------------------------------------------------
+DPDK kernel module is incompatible with Linux kernel version 3.3
+----------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
-| Title | Intel® DPDK kernel module is incompatible with Linux kernel version 3.3 |
+| Title | DPDK kernel module is incompatible with Linux kernel version 3.3 |
| | |
+=================================+=======================================================================================+
| Reference # | IXA00373232 |
@@ -430,7 +430,7 @@ Port not found issue with Intel® 82580 Gigabit Ethernet Controller
+---------------------------------+---------------------------------------------------------------------------------------+
| Description | After going through multiple driver unbind/bind cycles, an Intel® 82580 |
| | Ethernet Controller port may no longer be found and initialized by the |
-| | Intel® DPDK. |
+| | DPDK. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Implication | The port will be unusable. |
@@ -506,8 +506,8 @@ Promiscuous mode for 82580 NICs can only be enabled after a call to rte_eth_dev_
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-Incorrect CPU socket information reported in /proc/cpuinfo can prevent the Intel® DPDK from running
----------------------------------------------------------------------------------------------------
+Incorrect CPU socket information reported in /proc/cpuinfo can prevent the DPDK from running
+--------------------------------------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
| Title | Incorrect CPU socket information reported in /proc/cpuinfo can prevent the Intel® |
@@ -517,14 +517,14 @@ Incorrect CPU socket information reported in /proc/cpuinfo can prevent the Intel
| Reference # | 63 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Description | The Intel® DPDK users information supplied by the Linux kernel to determine the |
+| Description | The DPDK users information supplied by the Linux kernel to determine the |
| | hardware properties of the system being used. On rare occasions, information supplied |
| | by /proc/cpuinfo does not match that reported elsewhere. In some cases, it has been |
| | observed that the CPU socket numbering given in /proc/cpuinfo is incorrect and this |
-| | can prevent Intel® DPDK from operating. |
+| | can prevent DPDK from operating. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Implication | The Intel® DPDK cannot run on systems where /proc/cpuinfo does not report the correct |
+| Implication | The DPDK cannot run on systems where /proc/cpuinfo does not report the correct |
| | CPU socket topology. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -578,7 +578,7 @@ L3FWD-VF might lose CRC bytes
| Description | Currently, the CRC stripping configuration does not affect the VF driver. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Implication | Packets transmitted by the Intel® DPDK in the VM may be lacking 4 bytes (packet CRC). |
+| Implication | Packets transmitted by the DPDK in the VM may be lacking 4 bytes (packet CRC). |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Resolution/ Workaround | Set “strip_crc” to 1 in the sample applications that use the VF PMD. |
@@ -591,8 +591,8 @@ L3FWD-VF might lose CRC bytes
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-32-bit Intel® DPDK sample applications fails when using more than one 1 GB hugepage
------------------------------------------------------------------------------------
+32-bit DPDK sample applications fails when using more than one 1 GB hugepage
+----------------------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
| Title | 32-bit Intel® DPDK sample applications fails when using more than one 1 GB hugepage |
@@ -646,11 +646,11 @@ l2fwd fails to launch if the NIC is the Intel® 82571EB Gigabit Ethernet Control
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-32-bit Intel® DPDK applications may fail to initialize on 64-bit OS
--------------------------------------------------------------------
+32-bit DPDK applications may fail to initialize on 64-bit OS
+------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
-| Title | 32-bit Intel® DPDK applications may fail to initialize on 64-bit OS |
+| Title | 32-bit DPDK applications may fail to initialize on 64-bit OS |
| | |
+=================================+=======================================================================================+
| Reference # | IXA00378513 |
@@ -739,12 +739,12 @@ Config file change can cause build to fail
| Reference # | IXA00369247 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Description | If a change in a config file results in some Intel® DPDK files that were needed no |
+| Description | If a change in a config file results in some DPDK files that were needed no |
| | longer being needed, the build will fail. This is because the \*.o file will still |
| | exist, and the linker will try to link it. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Implication | Intel® DPDK compilation failure |
+| Implication | DPDK compilation failure |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Resolution | The Makefile now provides instructions to clean out old kernel module object files. |
@@ -768,8 +768,8 @@ rte_cmdline library should not be used in production code due to limited testing
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Description | The rte_cmdline library provides a command line interface for use in sample |
-| | applications and test applications distributed as part of Intel® DPDK. However, it is |
-| | not validated to the same standard as other Intel® DPDK libraries. |
+| | applications and test applications distributed as part of DPDK. However, it is |
+| | not validated to the same standard as other DPDK libraries. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Implication | It may contain bugs or errors that could cause issues in production applications. |
@@ -1017,18 +1017,18 @@ EAL can silently reserve less memory than requested
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-SSH connectivity with the board may be lost when starting an Intel® DPDK application
-------------------------------------------------------------------------------------
+SSH connectivity with the board may be lost when starting a DPDK application
+----------------------------------------------------------------------------
+---------------------------------+---------------------------------------------------------------------------------------+
-| Title | SSH connectivity with the board may be lost when starting an Intel® DPDK application |
+| Title | SSH connectivity with the board may be lost when starting a DPDK application |
| | |
+=================================+=======================================================================================+
| Reference # | 26 |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Description | Currently, the Intel® DPDK takes over all the NICs found on the board that are |
-| | supported by the Intel® DPDK. This results in these NICs being removed from the NIC |
+| | supported by the DPDK. This results in these NICs being removed from the NIC |
| | set handled by the kernel,which has the side effect of any SSH connection being |
| | terminated. See also issue #27. |
| | |
@@ -1036,8 +1036,8 @@ SSH connectivity with the board may be lost when starting an Intel® DPDK applic
| Implication | Loss of network connectivity to board. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution | Intel® DPDK now no longer binds ports on startup. Please refer to the Getting Started |
-| | Guide for information on how to bind/unbind ports from Intel® DPDK. |
+| Resolution | DPDK now no longer binds ports on startup. Please refer to the Getting Started |
+| | Guide for information on how to bind/unbind ports from DPDK. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Affected Environment/Platform | Systems using a Intel®DPDK supported NIC for remote system access |
@@ -1065,12 +1065,12 @@ Remote network connections lost when running autotests or sample applications
| Implication | Loss of network connectivity to board when connected remotely. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution | Intel® DPDK now no longer binds ports on startup. |
+| Resolution | DPDK now no longer binds ports on startup. |
| | Please refer to the Getting Started Guide for information on how to bind/unbind ports |
-| | from Intel® DPDK. |
+| | from DPDK. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Affected Environment/Platform | Systems using a Intel® DPDK supported NIC for remote system access |
+| Affected Environment/Platform | Systems using a DPDK supported NIC for remote system access |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Driver/Module | Sample applications |
@@ -1089,10 +1089,10 @@ KNI may not work properly in a multi-process environment
+---------------------------------+---------------------------------------------------------------------------------------+
| Description | Some of the network interface operations such as, MTU change or link UP/DOWN, when |
| | executed on KNI interface, might fail in a multi-process environment, although they |
-| | are normally successful in the Intel® DPDK single process environment. |
+| | are normally successful in the DPDK single process environment. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Implication | Some network interface operations on KNI cannot be used in an Intel® DPDK |
+| Implication | Some network interface operations on KNI cannot be used in a DPDK |
| | multi-process environment. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -1119,14 +1119,14 @@ Hash library cannot be used in multi-process applications with multiple binaries
| Description | The hash function used by a given hash-table implementation is referenced in the code |
| | by way of a function pointer. This means that it cannot work in cases where the hash |
| | function is at a different location in the code segment in different processes, as is |
-| | the case where an Intel® DPDK multi-process application uses a number of different |
+| | the case where a DPDK multi-process application uses a number of different |
| | binaries, for example, the client-server multi-process example. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
| Implication | The Hash library will not work if shared by multiple processes. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution/Workaround | New API was added for multiprocess scenario. Please refer to Intel® DPDK Programmer’s |
+| Resolution/Workaround | New API was added for multiprocess scenario. Please refer to DPDK Programmer’s |
| | Guide for more information. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
@@ -1182,7 +1182,7 @@ Packet reception issues when virtualization is enabled
| Implication | An application requiring packet transmission or reception will not function. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
-| Resolution/Workaround | Intel® DPDK Poll Mode Driver now has the ability to map correct physical addresses to |
+| Resolution/Workaround | DPDK Poll Mode Driver now has the ability to map correct physical addresses to |
| | the device structures. |
| | |
+---------------------------------+---------------------------------------------------------------------------------------+
diff --git a/doc/guides/rel_notes/supported_features.rst b/doc/guides/rel_notes/supported_features.rst
index 7efeff3..37e5416 100644
--- a/doc/guides/rel_notes/supported_features.rst
+++ b/doc/guides/rel_notes/supported_features.rst
@@ -61,7 +61,7 @@ Supported Features
* Virtualization (Xen)
- * Support for Intel® DPDK application running on Xen Domain0 without hugepages.
+ * Support for DPDK application running on Xen Domain0 without hugepages.
* Para-virtualization
@@ -70,7 +70,7 @@ Supported Features
Support userspace packet switching back-end example in host domain
* FreeBSD* 9.2 support for librte_pmd_e1000, librte_pmd_ixgbe and Virtual Function variants.
- Please refer to the *Intel® DPDK for FreeBSD\* Getting Started Guide*.
+ Please refer to the *DPDK for FreeBSD\* Getting Started Guide*.
Application support has been added for the following:
* multiprocess/symmetric_mp
@@ -87,7 +87,7 @@ Supported Features
* New VMXNET3 driver for the paravirtual device presented to a VM by the VMware* ESXi Hypervisor.
-* BETA: example support for basic Netmap applications on Intel® DPDK
+* BETA: example support for basic Netmap applications on DPDK
* Support for the wireless KASUMI algorithm in the dpdk_qat sample application
@@ -157,7 +157,7 @@ Supported Features
* Improved scalability for scheduling large numbers of timers using the rte_timer library
-* Support for building the Intel® DPDK as a shared library
+* Support for building the DPDK as a shared library
* Support for Intel® Ethernet Server Bypass Adapter X520-SR2
@@ -362,7 +362,7 @@ Supported Features
* Header files for common protocols (IP, SCTP, TCP, UDP)
-* Improved multi-process application support, allowing multiple co-operating Intel® DPDK
+* Improved multi-process application support, allowing multiple co-operating DPDK
processes to access the NIC port queues directly.
* CPU-specific compiler optimization
diff --git a/doc/guides/rel_notes/supported_os.rst b/doc/guides/rel_notes/supported_os.rst
index fb23dda..739cb2c 100644
--- a/doc/guides/rel_notes/supported_os.rst
+++ b/doc/guides/rel_notes/supported_os.rst
@@ -46,4 +46,4 @@ The following Linux* distributions were successfully used to generate or run the
* SUSE Enterprise Linux* 11 SP2
These distributions may need additional packages that are not installed by default, or a specific kernel.
-Refer to the *Intel® DPDK Getting Started Guide* for details.
+Refer to the *DPDK Getting Started Guide* for details.
diff --git a/doc/guides/rel_notes/updating_apps.rst b/doc/guides/rel_notes/updating_apps.rst
index ba8012d..034554d 100644
--- a/doc/guides/rel_notes/updating_apps.rst
+++ b/doc/guides/rel_notes/updating_apps.rst
@@ -1,11 +1,15 @@
Updating Applications from Previous Versions
============================================
-Although backward compatibility is being maintained across Intel® DPDK releases, code written for previous versions of the Intel® DPDK
-may require some code updates to benefit from performance and user experience enhancements provided in later Intel® DPDK releases.
+Although backward compatibility is being maintained across DPDK releases, code written for previous versions of the DPDK
+may require some code updates to benefit from performance and user experience enhancements provided in later DPDK releases.
-Intel® DPDK 1.6 to Intel® DPDK 1.7
-----------------------------------
+DPDK 1.7 to DPDK 1.8
+--------------------
+
+
+Intel® DPDK 1.6 to DPDK 1.7
+---------------------------
Note the following difference between 1.6 and 1.7:
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 7/8] doc: updated resolved issues with old known issues
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
` (5 preceding siblings ...)
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 6/8] doc: removed reference to Intel DPDK in Rel Notes Pablo de Lara
@ 2014-12-17 16:58 ` Pablo de Lara
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 8/8] doc: updating the list of sample apps in rel notes Pablo de Lara
7 siblings, 0 replies; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:58 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Removed resolved issues from known issues section.
Added new resolved issues to resolved issues section.
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
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
------------------------------------------------------------------------------------
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread* [dpdk-dev] [PATCH v4 8/8] doc: updating the list of sample apps in rel notes
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 0/8] doc: patch set to update release notes Pablo de Lara
` (6 preceding siblings ...)
2014-12-17 16:58 ` [dpdk-dev] [PATCH v4 7/8] doc: updated resolved issues with old known issues Pablo de Lara
@ 2014-12-17 16:58 ` Pablo de Lara
7 siblings, 0 replies; 49+ messages in thread
From: Pablo de Lara @ 2014-12-17 16:58 UTC (permalink / raw)
To: dev
From: Siobhan Butler <siobhan.a.butler@intel.com>
Added new and existing names of sample apps to list of
sample apps in release notes.
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
---
doc/guides/rel_notes/rel_description.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/rel_notes/rel_description.rst b/doc/guides/rel_notes/rel_description.rst
index 8da53c4..49f32b9 100644
--- a/doc/guides/rel_notes/rel_description.rst
+++ b/doc/guides/rel_notes/rel_description.rst
@@ -113,10 +113,14 @@ The following is a list of DPDK documents in the suggested reading order:
* L3 Forwarding
+ * L3 Forwarding with Access Control
+
* L3 Forwarding with Power Management
* L3 Forwarding in a Virtualized Environment
+ * Link Status Interrupt
+
* Load Balancing
* Multi-process
@@ -143,6 +147,8 @@ The following is a list of DPDK documents in the suggested reading order:
* VM Power Management
+ * Distributor
+
In addition, there are some other applications that are built when the libraries are created.
The source for these applications is in the DPDK/app directory and are called:
--
2.1.0
^ permalink raw reply [flat|nested] 49+ messages in thread