[dpdk-dev] doc: drop old naming of the project
Commit Message
It was requested by Intel, more than one year ago, to replace the name
"Intel DPDK" by "DPDK".
Some references to the old name were still in some docs and code comments,
leading to confusion.
Fixes: ac8ada004c12 ("doc: remove Intel references from release notes")
Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
doc/guides/linux_gsg/intro.rst | 2 +-
doc/guides/nics/intel_vf.rst | 2 +-
doc/guides/nics/pcap_ring.rst | 2 +-
doc/guides/prog_guide/{extend_intel_dpdk.rst => extend_dpdk.rst} | 0
doc/guides/prog_guide/index.rst | 4 ++--
...ty_intel_dpdk_functions.rst => thread_safety_dpdk_functions.rst} | 0
doc/guides/rel_notes/known_issues.rst | 6 +++---
doc/guides/sample_app_ug/cmd_line.rst | 2 +-
examples/ip_pipeline/config/tm_profile.cfg | 2 +-
examples/qos_sched/profile.cfg | 2 +-
lib/librte_eal/common/include/rte_common.h | 2 +-
lib/librte_eal/common/include/rte_eal.h | 2 +-
lib/librte_eal/common/include/rte_version.h | 2 +-
lib/librte_pipeline/rte_pipeline.h | 2 +-
lib/librte_port/rte_port.h | 2 +-
lib/librte_table/rte_table.h | 2 +-
16 files changed, 17 insertions(+), 17 deletions(-)
rename doc/guides/prog_guide/{extend_intel_dpdk.rst => extend_dpdk.rst} (100%)
rename doc/guides/prog_guide/{thread_safety_intel_dpdk_functions.rst => thread_safety_dpdk_functions.rst} (100%)
Comments
On Mon, Feb 08, 2016 at 02:39:02PM +0100, Thomas Monjalon wrote:
> It was requested by Intel, more than one year ago, to replace the name
> "Intel DPDK" by "DPDK".
> Some references to the old name were still in some docs and code comments,
> leading to confusion.
>
> Fixes: ac8ada004c12 ("doc: remove Intel references from release notes")
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2016-02-09 17:20, Bruce Richardson:
> On Mon, Feb 08, 2016 at 02:39:02PM +0100, Thomas Monjalon wrote:
> > It was requested by Intel, more than one year ago, to replace the name
> > "Intel DPDK" by "DPDK".
> > Some references to the old name were still in some docs and code comments,
> > leading to confusion.
> >
> > Fixes: ac8ada004c12 ("doc: remove Intel references from release notes")
> >
> > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied
@@ -31,7 +31,7 @@
Introduction
============
-This document contains instructions for installing and configuring the Intel® Data Plane Development Kit (DPDK) software.
+This document contains instructions for installing and configuring the Data Plane Development Kit (DPDK) software.
It is designed to get customers up and running quickly.
The document describes how to compile and run a DPDK application in a Linux application (linuxapp) environment,
without going deeply into detail.
@@ -278,7 +278,7 @@ For example,
rmmod igb (To remove the igb module)
insmod igb max_vfs=2,2 (To enable two Virtual Functions per port)
-* Using Intel® DPDK PMD PF igb driver:
+* Using DPDK PMD PF igb driver:
Kernel Params: iommu=pt, intel_iommu=on modprobe uio
@@ -45,7 +45,7 @@ the DPDK also includes two pure-software PMDs. These two drivers are:
The libpcap -based PMD is disabled by default in the build configuration files,
owing to an external dependency on the libpcap development files which must be installed on the board.
Once the libpcap development files are installed,
- the library can be enabled by setting CONFIG_RTE_LIBRTE_PMD_PCAP=y and recompiling the Intel® DPDK.
+ the library can be enabled by setting CONFIG_RTE_LIBRTE_PMD_PCAP=y and recompiling the DPDK.
Using the Drivers from the EAL Command Line
-------------------------------------------
similarity index 100%
rename from doc/guides/prog_guide/extend_intel_dpdk.rst
rename to doc/guides/prog_guide/extend_dpdk.rst
@@ -53,7 +53,7 @@ Programmer's Guide
ip_fragment_reassembly_lib
multi_proc_support
kernel_nic_interface
- thread_safety_intel_dpdk_functions
+ thread_safety_dpdk_functions
qos_framework
power_man
packet_classif_access_ctrl
@@ -63,7 +63,7 @@ Programmer's Guide
source_org
dev_kit_build_system
dev_kit_root_make_help
- extend_intel_dpdk
+ extend_dpdk
build_app
ext_app_lib_make_help
perf_opt_guidelines
similarity index 100%
rename from doc/guides/prog_guide/thread_safety_intel_dpdk_functions.rst
rename to doc/guides/prog_guide/thread_safety_dpdk_functions.rst
@@ -163,7 +163,7 @@ Not all variants of supported NIC types have been used in testing
**Description**:
The supported network interface cards can come in a number of variants with different device ID's.
- Not all of these variants have been tested with the Intel® DPDK.
+ Not all of these variants have been tested with the DPDK.
The NIC device identifiers used during testing:
@@ -210,7 +210,7 @@ Multi-process sample app requires exact memory mapping
A multi-process client application fails to initialize.
**Resolution/Workaround**:
- See the "Multi-process Limitations" section in the Intel® DPDK Programmer's Guide for more information.
+ See the "Multi-process Limitations" section in the DPDK Programmer's Guide for more information.
**Affected Environment/Platform**:
All.
@@ -468,7 +468,7 @@ GCC might generate Intel® AVX instructions for processors without Intel® AVX s
------------------------------------------------------------------------------------
**Description**:
- When compiling Intel® DPDK (and any DPDK app), gcc may generate Intel® AVX instructions, even when the
+ When compiling DPDK (and any DPDK app), gcc may generate Intel® AVX instructions, even when the
processor does not support Intel® AVX.
**Implication**:
@@ -45,7 +45,7 @@ to debug a DPDK application, in a Linux* application environment.
.. note::
The rte_cmdline library should not be used in production code since
- it is not validated to the same standard as other Intel® DPDK libraries.
+ it is not validated to the same standard as other DPDK libraries.
See also the "rte_cmdline library should not be used in production code due to limited testing" item
in the "Known Issues" section of the Release Notes.
@@ -41,7 +41,7 @@
; are set to 1:1:1:1
;
; For more details, please refer to chapter "Quality of Service (QoS) Framework"
-; of Intel Data Plane Development Kit (Intel DPDK) Programmer's Guide.
+; of Data Plane Development Kit (DPDK) Programmer's Guide.
; Port configuration
[port]
@@ -41,7 +41,7 @@
; are set to 1:1:1:1
;
; For more details, please refer to chapter "Quality of Service (QoS) Framework"
-; of Intel Data Plane Development Kit (Intel DPDK) Programmer's Guide.
+; of Data Plane Development Kit (DPDK) Programmer's Guide.
; Port configuration
[port]
@@ -38,7 +38,7 @@
* @file
*
* Generic, commonly-used macro and inline function definitions
- * for Intel DPDK.
+ * for DPDK.
*/
#ifdef __cplusplus
@@ -86,7 +86,7 @@ struct rte_config {
/**
* Pointer to memory configuration, which may be shared across multiple
- * Intel DPDK instances
+ * DPDK instances
*/
struct rte_mem_config *mem_config;
} __attribute__((__packed__));
@@ -33,7 +33,7 @@
/**
* @file
- * Definitions of Intel(R) DPDK version numbers
+ * Definitions of DPDK version numbers
*/
#ifndef _RTE_VERSION_H_
@@ -42,7 +42,7 @@ extern "C" {
* @file
* RTE Pipeline
*
- * This tool is part of the Intel DPDK Packet Framework tool suite and provides
+ * This tool is part of the DPDK Packet Framework tool suite and provides
* a standard methodology (logically similar to OpenFlow) for rapid development
* of complex packet processing pipelines out of ports, tables and actions.
*
@@ -42,7 +42,7 @@ extern "C" {
* @file
* RTE Port
*
- * This tool is part of the Intel DPDK Packet Framework tool suite and provides
+ * This tool is part of the DPDK Packet Framework tool suite and provides
* a standard interface to implement different types of packet ports.
*
***/
@@ -42,7 +42,7 @@ extern "C" {
* @file
* RTE Table
*
- * This tool is part of the Intel DPDK Packet Framework tool suite and provides
+ * This tool is part of the DPDK Packet Framework tool suite and provides
* a standard interface to implement different types of lookup tables for data
* plane processing.
*