From: Kevin Traynor <ktraynor@redhat.com>
To: John McNamara <john.mcnamara@intel.com>
Cc: Rami Rosen <ramirose@gmail.com>, dpdk stable <stable@dpdk.org>
Subject: [dpdk-stable] patch 'doc: fix spelling reported by aspell in guides' has been queued to LTS release 18.11.2
Date: Wed, 8 May 2019 17:02:00 +0100 [thread overview]
Message-ID: <20190508160233.2648-3-ktraynor@redhat.com> (raw)
In-Reply-To: <20190508160233.2648-1-ktraynor@redhat.com>
Hi,
FYI, your patch has been queued to LTS release 18.11.2
Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 05/14/19. So please
shout if anyone has objections.
Also note that after the patch there's a diff of the upstream commit vs the
patch applied to the branch. This will indicate if there was any rebasing
needed to apply to the stable branch. If there were code changes for rebasing
(ie: not only metadata diffs), please double check that the rebase was
correctly done.
Queued patches are on a temporary branch at:
https://github.com/kevintraynor/dpdk-stable-queue
This queued commit can be viewed at:
https://github.com/kevintraynor/dpdk-stable-queue/commit/8ca6a5b8794806d131f4bd3faf776894d8ecd90a
Thanks.
Kevin Traynor
---
From 8ca6a5b8794806d131f4bd3faf776894d8ecd90a Mon Sep 17 00:00:00 2001
From: John McNamara <john.mcnamara@intel.com>
Date: Fri, 26 Apr 2019 16:14:21 +0100
Subject: [PATCH] doc: fix spelling reported by aspell in guides
[ upstream commit d629b7b5fe812f0040b83d27d2ada33b003aa918 ]
Fix spelling errors in the guide docs.
Signed-off-by: John McNamara <john.mcnamara@intel.com>
Acked-by: Rami Rosen <ramirose@gmail.com>
---
doc/guides/compressdevs/overview.rst | 2 +-
doc/guides/contributing/patches.rst | 2 +-
doc/guides/cryptodevs/aesni_mb.rst | 2 +-
doc/guides/cryptodevs/overview.rst | 2 +-
doc/guides/cryptodevs/scheduler.rst | 2 +-
doc/guides/eventdevs/opdl.rst | 2 +-
doc/guides/eventdevs/sw.rst | 4 +--
doc/guides/howto/lm_bond_virtio_sriov.rst | 2 +-
doc/guides/howto/lm_virtio_vhost_user.rst | 4 +--
doc/guides/howto/rte_flow.rst | 6 ++--
.../howto/virtio_user_as_exceptional_path.rst | 8 +++---
doc/guides/nics/atlantic.rst | 2 +-
doc/guides/nics/cxgbe.rst | 4 +--
doc/guides/nics/dpaa.rst | 2 +-
doc/guides/nics/dpaa2.rst | 2 +-
doc/guides/nics/enetc.rst | 2 +-
doc/guides/nics/enic.rst | 2 +-
doc/guides/nics/features.rst | 2 +-
doc/guides/nics/i40e.rst | 2 +-
doc/guides/nics/ixgbe.rst | 4 +--
doc/guides/nics/kni.rst | 2 +-
doc/guides/nics/mlx5.rst | 2 +-
doc/guides/nics/mvpp2.rst | 2 +-
doc/guides/nics/netvsc.rst | 2 +-
doc/guides/nics/sfc_efx.rst | 14 +++++-----
doc/guides/nics/szedata2.rst | 2 +-
doc/guides/nics/tap.rst | 2 +-
doc/guides/platform/dpaa.rst | 4 +--
doc/guides/platform/dpaa2.rst | 4 +--
doc/guides/prog_guide/bbdev.rst | 4 +--
doc/guides/prog_guide/compressdev.rst | 6 ++--
doc/guides/prog_guide/cryptodev_lib.rst | 12 ++++----
.../prog_guide/dev_kit_build_system.rst | 2 +-
doc/guides/prog_guide/efd_lib.rst | 2 +-
.../prog_guide/env_abstraction_layer.rst | 2 +-
.../prog_guide/event_ethernet_rx_adapter.rst | 6 ++--
doc/guides/prog_guide/eventdev.rst | 6 ++--
.../prog_guide/kernel_nic_interface.rst | 2 +-
doc/guides/prog_guide/metrics_lib.rst | 2 +-
doc/guides/prog_guide/multi_proc_support.rst | 2 +-
doc/guides/prog_guide/profile_app.rst | 4 +--
doc/guides/prog_guide/rte_flow.rst | 8 +++---
doc/guides/prog_guide/rte_security.rst | 20 ++++++-------
doc/guides/prog_guide/traffic_management.rst | 2 +-
doc/guides/prog_guide/vhost_lib.rst | 2 +-
doc/guides/rawdevs/ifpga_rawdev.rst | 2 +-
doc/guides/rel_notes/known_issues.rst | 8 +++---
doc/guides/rel_notes/release_17_11.rst | 10 +++----
doc/guides/sample_app_ug/bbdev_app.rst | 4 +--
.../sample_app_ug/eventdev_pipeline.rst | 2 +-
doc/guides/sample_app_ug/intro.rst | 2 +-
doc/guides/sample_app_ug/ip_pipeline.rst | 4 +--
doc/guides/sample_app_ug/ipsec_secgw.rst | 4 +--
.../sample_app_ug/performance_thread.rst | 4 +--
doc/guides/sample_app_ug/qos_metering.rst | 2 +-
doc/guides/sample_app_ug/test_pipeline.rst | 2 +-
doc/guides/sample_app_ug/vhost.rst | 4 +--
doc/guides/sample_app_ug/vhost_scsi.rst | 2 +-
.../sample_app_ug/vm_power_management.rst | 10 +++----
doc/guides/testpmd_app_ug/run_app.rst | 10 +++----
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 28 +++++++++----------
doc/guides/tools/cryptoperf.rst | 22 +++++++--------
doc/guides/tools/proc_info.rst | 2 +-
doc/guides/tools/testbbdev.rst | 2 +-
64 files changed, 149 insertions(+), 149 deletions(-)
diff --git a/doc/guides/compressdevs/overview.rst b/doc/guides/compressdevs/overview.rst
index 70bbe82b7..809e4e6e7 100644
--- a/doc/guides/compressdevs/overview.rst
+++ b/doc/guides/compressdevs/overview.rst
@@ -19,5 +19,5 @@ Supported Feature Flags
- "OOP SGL In SGL Out" feature flag stands for
- "Out-of-place Scatter-gather list Input, Scatter-gater list Output",
+ "Out-of-place Scatter-gather list Input, Scatter-gather list Output",
which means PMD supports different scatter-gather styled input and output buffers
(i.e. both can consists of multiple segments).
diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
index a64bb0368..427137dc7 100644
--- a/doc/guides/contributing/patches.rst
+++ b/doc/guides/contributing/patches.rst
@@ -9,5 +9,5 @@ Contributing Code to DPDK
This document outlines the guidelines for submitting code to DPDK.
-The DPDK development process is modelled (loosely) on the Linux Kernel development model so it is worth reading the
+The DPDK development process is modeled (loosely) on the Linux Kernel development model so it is worth reading the
Linux kernel guide on submitting patches:
`How to Get Your Change Into the Linux Kernel <https://www.kernel.org/doc/html/latest/process/submitting-patches.html>`_.
diff --git a/doc/guides/cryptodevs/aesni_mb.rst b/doc/guides/cryptodevs/aesni_mb.rst
index d9fd41ae5..ccfc137f1 100644
--- a/doc/guides/cryptodevs/aesni_mb.rst
+++ b/doc/guides/cryptodevs/aesni_mb.rst
@@ -126,5 +126,5 @@ For AES Counter mode (AES-CTR), the library supports two different sizes for Ini
Vector (IV):
-* 12 bytes: used mainly for IPSec, as it requires 12 bytes from the user, which internally
+* 12 bytes: used mainly for IPsec, as it requires 12 bytes from the user, which internally
are appended the counter block (4 bytes), which is set to 1 for the first block
(no padding required from the user)
diff --git a/doc/guides/cryptodevs/overview.rst b/doc/guides/cryptodevs/overview.rst
index 407f063de..f9f8c7bec 100644
--- a/doc/guides/cryptodevs/overview.rst
+++ b/doc/guides/cryptodevs/overview.rst
@@ -19,5 +19,5 @@ Supported Feature Flags
- "OOP SGL In SGL Out" feature flag stands for
- "Out-of-place Scatter-gather list Input, Scatter-gater list Output",
+ "Out-of-place Scatter-gather list Input, Scatter-gather list Output",
which means pmd supports different scatter-gather styled input and output buffers
(i.e. both can consists of multiple segments).
diff --git a/doc/guides/cryptodevs/scheduler.rst b/doc/guides/cryptodevs/scheduler.rst
index a754a27e6..7004ca431 100644
--- a/doc/guides/cryptodevs/scheduler.rst
+++ b/doc/guides/cryptodevs/scheduler.rst
@@ -166,5 +166,5 @@ operation:
an optimal solution, as it doesn't give significant per-core performance improvement.
For mixed traffic (IMIX) the optimal number of worker cores is around 2-3.
- For large packets (1.5 Kbytes) scheduler shows linear scaling in performance
+ For large packets (1.5 kbytes) scheduler shows linear scaling in performance
up to eight cores.
Each worker uses its own slave cryptodev. Only software cryptodevs
diff --git a/doc/guides/eventdevs/opdl.rst b/doc/guides/eventdevs/opdl.rst
index 0262a337a..979f6cd8d 100644
--- a/doc/guides/eventdevs/opdl.rst
+++ b/doc/guides/eventdevs/opdl.rst
@@ -9,5 +9,5 @@ implementation of the eventdev API. It is particularly suited to packet\
processing workloads that have high throughput and low latency requirements.\
All packets follow the same path through the device. The order in which\
-packets follow is determinted by the order in which queues are set up.\
+packets follow is determined by the order in which queues are set up.\
Events are left on the ring until they are transmitted. As a result packets\
do not go out of order
diff --git a/doc/guides/eventdevs/sw.rst b/doc/guides/eventdevs/sw.rst
index afdcad760..04c8b0305 100644
--- a/doc/guides/eventdevs/sw.rst
+++ b/doc/guides/eventdevs/sw.rst
@@ -71,5 +71,5 @@ The credit quanta is the number of credits that a port will fetch at a time from
the instance's credit pool. Higher numbers will cause less overhead in the
atomic credit fetch code, however it also reduces the overall number of credits
-in the system faster. A balanced number (eg 32) ensures that only small numbers
+in the system faster. A balanced number (e.g. 32) ensures that only small numbers
of credits are pre-allocated at a time, while also mitigating performance impact
of the atomics.
@@ -101,5 +101,5 @@ feature would be significant.
The software eventdev does not support creating queues that handle all types of
-traffic. An eventdev with this capability allows enqueueing Atomic, Ordered and
+traffic. An eventdev with this capability allows enqueuing Atomic, Ordered and
Parallel traffic to the same queue, but scheduling each of them appropriately.
diff --git a/doc/guides/howto/lm_bond_virtio_sriov.rst b/doc/guides/howto/lm_bond_virtio_sriov.rst
index a47d6dbf8..4e5ef4d56 100644
--- a/doc/guides/howto/lm_bond_virtio_sriov.rst
+++ b/doc/guides/howto/lm_bond_virtio_sriov.rst
@@ -329,5 +329,5 @@ On host_server_2: Terminal 1
.. code-block:: console
- testomd> show port info all
+ testpmd> show port info all
testpmd> show port stats all
testpmd> show bonding config 2
diff --git a/doc/guides/howto/lm_virtio_vhost_user.rst b/doc/guides/howto/lm_virtio_vhost_user.rst
index 3f5ebd58a..019c124d4 100644
--- a/doc/guides/howto/lm_virtio_vhost_user.rst
+++ b/doc/guides/howto/lm_virtio_vhost_user.rst
@@ -244,5 +244,5 @@ On host_server_2: Terminal 1
.. code-block:: console
- testomd> show port info all
+ testpmd> show port info all
testpmd> show port stats all
@@ -339,5 +339,5 @@ reset_vf_on_212_131.sh
# This script is run on the host 10.237.212.131 to reset SRIOV
- # BDF for Ninatic NIC is 0000:06:00.0
+ # BDF for Niantic NIC is 0000:06:00.0
cat /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
echo 0 > /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
diff --git a/doc/guides/howto/rte_flow.rst b/doc/guides/howto/rte_flow.rst
index 6a8534d98..e080570e9 100644
--- a/doc/guides/howto/rte_flow.rst
+++ b/doc/guides/howto/rte_flow.rst
@@ -24,5 +24,5 @@ destination equals 192.168.3.2. This code is equivalent to the following
testpmd command (wrapped for clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan /
+ testpmd> flow create 0 ingress pattern eth / vlan /
ipv4 dst is 192.168.3.2 / end actions drop / end
@@ -119,5 +119,5 @@ This code is equivalent to the following testpmd command (wrapped for
clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan /
+ testpmd> flow create 0 ingress pattern eth / vlan /
ipv4 dst spec 192.168.3.0 dst mask 255.255.255.0 /
end actions drop / end
@@ -220,5 +220,5 @@ This code is equivalent to the following testpmd command (wrapped for
clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan vid spec 123 /
+ testpmd> flow create 0 ingress pattern eth / vlan vid spec 123 /
end actions queue index 3 / end
diff --git a/doc/guides/howto/virtio_user_as_exceptional_path.rst b/doc/guides/howto/virtio_user_as_exceptional_path.rst
index 4910c12df..ec021af39 100644
--- a/doc/guides/howto/virtio_user_as_exceptional_path.rst
+++ b/doc/guides/howto/virtio_user_as_exceptional_path.rst
@@ -2,5 +2,5 @@
Copyright(c) 2016 Intel Corporation.
-.. _virtio_user_as_excpetional_path:
+.. _virtio_user_as_exceptional_path:
Virtio_user as Exceptional Path
@@ -23,5 +23,5 @@ solution is very promising in:
vhost-net is born to be a networking solution, which has lots of networking
- related featuers, like multi queue, tso, multi-seg mbuf, etc.
+ related features, like multi queue, tso, multi-seg mbuf, etc.
* Performance
@@ -39,5 +39,5 @@ in :numref:`figure_virtio_user_as_exceptional_path`.
.. figure:: img/virtio_user_as_exceptional_path.*
- Overview of a DPDK app using virtio-user as excpetional path
+ Overview of a DPDK app using virtio-user as exceptional path
@@ -76,5 +76,5 @@ compiling the kernel and those kernel modules should be inserted.
* ``queues``
- Number of multi-queues. Each qeueue will be served by a kthread. For example:
+ Number of multi-queues. Each queue will be served by a kthread. For example:
.. code-block:: console
diff --git a/doc/guides/nics/atlantic.rst b/doc/guides/nics/atlantic.rst
index 80591b13c..f6f2c66bf 100644
--- a/doc/guides/nics/atlantic.rst
+++ b/doc/guides/nics/atlantic.rst
@@ -19,5 +19,5 @@ Supported features
- RSS (Receive Side Scaling)
- Checksum offload
-- Jumbo Frame upto 16K
+- Jumbo Frame up to 16K
Configuration Information
diff --git a/doc/guides/nics/cxgbe.rst b/doc/guides/nics/cxgbe.rst
index 58d88eef5..39106274e 100644
--- a/doc/guides/nics/cxgbe.rst
+++ b/doc/guides/nics/cxgbe.rst
@@ -127,5 +127,5 @@ enabling debugging options may affect system performance.
- ``CONFIG_RTE_LIBRTE_CXGBE_TPUT`` (default **y**)
- Toggle behaviour to prefer Throughput or Latency.
+ Toggle behavior to prefer Throughput or Latency.
Runtime Options
@@ -141,5 +141,5 @@ be passed as part of EAL arguments. For example,
- ``keep_ovlan`` (default **0**)
- Toggle behaviour to keep/strip outer VLAN in Q-in-Q packets. If
+ Toggle behavior to keep/strip outer VLAN in Q-in-Q packets. If
enabled, the outer VLAN tag is preserved in Q-in-Q packets. Otherwise,
the outer VLAN tag is stripped in Q-in-Q packets.
diff --git a/doc/guides/nics/dpaa.rst b/doc/guides/nics/dpaa.rst
index 2173673b9..5900ed0df 100644
--- a/doc/guides/nics/dpaa.rst
+++ b/doc/guides/nics/dpaa.rst
@@ -252,5 +252,5 @@ state during application initialization:
configuration beyond that will be standard Rx queues. The application can
choose to change their number if HW portals are limited.
- The valid values are from '0' to '4'. The valuse shall be set to '0' if the
+ The valid values are from '0' to '4'. The values shall be set to '0' if the
application want to use eventdev with DPAA device.
diff --git a/doc/guides/nics/dpaa2.rst b/doc/guides/nics/dpaa2.rst
index 769dc4e12..04370e4cd 100644
--- a/doc/guides/nics/dpaa2.rst
+++ b/doc/guides/nics/dpaa2.rst
@@ -380,5 +380,5 @@ DPBP based Mempool driver
~~~~~~~~~~~~~~~~~~~~~~~~~
-The DPBP driver is bound to a DPBP objects and provides sevices to
+The DPBP driver is bound to a DPBP objects and provides services to
create a hardware offloaded packet buffer mempool.
diff --git a/doc/guides/nics/enetc.rst b/doc/guides/nics/enetc.rst
index 8038bf205..376768d39 100644
--- a/doc/guides/nics/enetc.rst
+++ b/doc/guides/nics/enetc.rst
@@ -70,5 +70,5 @@ Prerequisites
~~~~~~~~~~~~~
-There are three main pre-requisities for executing ENETC PMD on a ENETC
+There are three main pre-requisites for executing ENETC PMD on a ENETC
compatible board:
diff --git a/doc/guides/nics/enic.rst b/doc/guides/nics/enic.rst
index 3b45b3b3f..c1b83b9b6 100644
--- a/doc/guides/nics/enic.rst
+++ b/doc/guides/nics/enic.rst
@@ -225,5 +225,5 @@ the use of SR-IOV.
-.. _enic-genic-flow-api:
+.. _enic-generic-flow-api:
Generic Flow API support
diff --git a/doc/guides/nics/features.rst b/doc/guides/nics/features.rst
index c5bf32222..d57ddc2ff 100644
--- a/doc/guides/nics/features.rst
+++ b/doc/guides/nics/features.rst
@@ -496,5 +496,5 @@ Inline crypto
-------------
-Supports inline crypto processing (eg. inline IPsec). See Security library and PMD documentation for more details.
+Supports inline crypto processing (e.g. inline IPsec). See Security library and PMD documentation for more details.
* **[uses] rte_eth_rxconf,rte_eth_rxmode**: ``offloads:DEV_RX_OFFLOAD_SECURITY``,
diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
index 40bf0f140..62e90d9fd 100644
--- a/doc/guides/nics/i40e.rst
+++ b/doc/guides/nics/i40e.rst
@@ -572,5 +572,5 @@ TC TX scheduling mode setting
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-There're 2 TX scheduling modes for TCs, round robin and strict priority mode.
+There are 2 TX scheduling modes for TCs, round robin and strict priority mode.
If a TC is set to strict priority mode, it can consume unlimited bandwidth.
It means if APP has set the max bandwidth for that TC, it comes to no
diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst
index 1c294b06a..975143f8b 100644
--- a/doc/guides/nics/ixgbe.rst
+++ b/doc/guides/nics/ixgbe.rst
@@ -204,6 +204,6 @@ X550 does not support legacy interrupt mode
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Desccription
-^^^^^^^^^^^^
+Description
+^^^^^^^^^^^
X550 cannot get interrupts if using ``uio_pci_generic`` module or using legacy
interrupt mode of ``igb_uio`` or ``vfio``. Because the errata of X550 states
diff --git a/doc/guides/nics/kni.rst b/doc/guides/nics/kni.rst
index 204fbd563..c4fc96373 100644
--- a/doc/guides/nics/kni.rst
+++ b/doc/guides/nics/kni.rst
@@ -65,5 +65,5 @@ PMD arguments
-------------
-``no_request_thread``, by default PMD creates a phtread for each KNI interface
+``no_request_thread``, by default PMD creates a pthread for each KNI interface
to handle Linux network interface control commands, like ``ifconfig kni0 up``
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index bfa6cf162..cee167bfe 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -169,5 +169,5 @@ Limitations
- must specify the tunnel outer VNI in the VXLAN item.
- must specify the tunnel outer remote (destination) UDP port in the VXLAN item.
- - must specify the tunnel outer local (source) IPv4 or IPv6 in the , this address will locally (with scope link) assigned to the outer network interace, wildcards not allowed.
+ - must specify the tunnel outer local (source) IPv4 or IPv6 in the , this address will locally (with scope link) assigned to the outer network interface, wildcards not allowed.
- must specify the tunnel outer remote (destination) IPv4 or IPv6 in the VXLAN item, group IPs allowed.
- must specify the tunnel outer destination MAC address in the VXLAN item, this address will be used to create neigh rule.
diff --git a/doc/guides/nics/mvpp2.rst b/doc/guides/nics/mvpp2.rst
index b2ddeab50..f63d85875 100644
--- a/doc/guides/nics/mvpp2.rst
+++ b/doc/guides/nics/mvpp2.rst
@@ -92,5 +92,5 @@ Limitations
- MUSDK architecture does not support changing configuration in run time.
- All nessesary configurations should be done before first dev_start().
+ All necessary configurations should be done before first dev_start().
- RX queue start/stop is not supported.
diff --git a/doc/guides/nics/netvsc.rst b/doc/guides/nics/netvsc.rst
index 87fabf5b8..6dbb9a551 100644
--- a/doc/guides/nics/netvsc.rst
+++ b/doc/guides/nics/netvsc.rst
@@ -90,5 +90,5 @@ operations:
.. Note::
- The dpkd-devbind.py script can not be used since it only handles PCI devices.
+ The dpdk-devbind.py script can not be used since it only handles PCI devices.
diff --git a/doc/guides/nics/sfc_efx.rst b/doc/guides/nics/sfc_efx.rst
index 40065284b..f449b19d6 100644
--- a/doc/guides/nics/sfc_efx.rst
+++ b/doc/guides/nics/sfc_efx.rst
@@ -97,5 +97,5 @@ Non-supported Features
The features not yet supported include:
-- Receive queue interupts
+- Receive queue interrupts
- Priority-based flow control
@@ -208,10 +208,10 @@ Supported actions:
Validating flow rules depends on the firmware variant.
-Ethernet destinaton individual/group match
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Ethernet destination individual/group match
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ethernet item supports I/G matching, if only the corresponding bit is set
-in the mask of destination address. If destinaton address in the spec is
-multicast, it matches all multicast (and broadcast) packets, oherwise it
+in the mask of destination address. If destination address in the spec is
+multicast, it matches all multicast (and broadcast) packets, otherwise it
matches unicast packets that are not filtered by other flow rules.
@@ -347,8 +347,8 @@ boolean parameters value.
- ``perf_profile`` [auto|throughput|low-latency] (default **throughput**)
- Choose hardware tunning to be optimized for either throughput or
+ Choose hardware tuning to be optimized for either throughput or
low-latency.
**auto** allows NIC firmware to make a choice based on
- installed licences and firmware variant configured using **sfboot**.
+ installed licenses and firmware variant configured using **sfboot**.
- ``stats_update_period_ms`` [long] (default **1000**)
diff --git a/doc/guides/nics/szedata2.rst b/doc/guides/nics/szedata2.rst
index a2092f9c5..94dba82d9 100644
--- a/doc/guides/nics/szedata2.rst
+++ b/doc/guides/nics/szedata2.rst
@@ -90,5 +90,5 @@ Ethernet port may be sent to any queue.
They were historically represented in DPDK as a single port.
-However, the new NFB-200G2QL card employs an addon cable which allows to connect
+However, the new NFB-200G2QL card employs an add-on cable which allows to connect
it to two physical PCI-E slots at the same time (see the diagram below).
This is done to allow 200 Gbps of traffic to be transferred through the PCI-E
diff --git a/doc/guides/nics/tap.rst b/doc/guides/nics/tap.rst
index 9a3d7b348..14c669b7b 100644
--- a/doc/guides/nics/tap.rst
+++ b/doc/guides/nics/tap.rst
@@ -41,5 +41,5 @@ actual MAC address: ``00:64:74:61:70:[00-FF]``.
The MAC address will have a user value passed as string. The MAC address is in
-format with delimeter ``:``. The string is byte converted to hex and you get
+format with delimiter ``:``. The string is byte converted to hex and you get
the actual MAC address: ``00:64:74:61:70:11``.
diff --git a/doc/guides/platform/dpaa.rst b/doc/guides/platform/dpaa.rst
index 390487152..6005f2221 100644
--- a/doc/guides/platform/dpaa.rst
+++ b/doc/guides/platform/dpaa.rst
@@ -5,5 +5,5 @@ NXP QorIQ DPAA Board Support Package
====================================
-This doc has information about steps to setup QorIq dpaa
+This doc has information about steps to setup QorIQ dpaa
based layerscape platform and information about common offload
hw block drivers of **NXP QorIQ DPAA** SoC family.
@@ -39,5 +39,5 @@ Steps To Setup Platform
-----------------------
-There are four main pre-requisities for executing DPAA PMD on a DPAA
+There are four main pre-requisites for executing DPAA PMD on a DPAA
compatible board:
diff --git a/doc/guides/platform/dpaa2.rst b/doc/guides/platform/dpaa2.rst
index 5a64406eb..2586af0ff 100644
--- a/doc/guides/platform/dpaa2.rst
+++ b/doc/guides/platform/dpaa2.rst
@@ -5,5 +5,5 @@ NXP QorIQ DPAA2 Board Support Package
=====================================
-This doc has information about steps to setup NXP QoriQ DPAA2 platform
+This doc has information about steps to setup NXP QorIQ DPAA2 platform
and information about common offload hw block drivers of
**NXP QorIQ DPAA2** SoC family.
@@ -49,5 +49,5 @@ Steps To Setup Platform
-----------------------
-There are four main pre-requisities for executing DPAA2 PMD on a DPAA2
+There are four main pre-requisites for executing DPAA2 PMD on a DPAA2
compatible board:
diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
index 9de14443e..658ffd400 100644
--- a/doc/guides/prog_guide/bbdev.rst
+++ b/doc/guides/prog_guide/bbdev.rst
@@ -79,5 +79,5 @@ one or more queues identified by queue IDs. While different devices may have
different capabilities (e.g. support different operation types), all queues on
a device support identical configuration possibilities. A queue is configured
-for only one type of operation and is configured at initializations time.
+for only one type of operation and is configured at initialization time.
When an operation is enqueued to a specific queue ID, the result is dequeued
from the same queue ID.
@@ -679,5 +679,5 @@ baseband processor capable of transceiving data packets.
The following sample C-like pseudo-code shows the basic steps to encode several
-buffers using (**sw_trubo**) bbdev PMD.
+buffers using (**sw_turbo**) bbdev PMD.
.. code-block:: c
diff --git a/doc/guides/prog_guide/compressdev.rst b/doc/guides/prog_guide/compressdev.rst
index 87e264906..3ba4238ce 100644
--- a/doc/guides/prog_guide/compressdev.rst
+++ b/doc/guides/prog_guide/compressdev.rst
@@ -18,5 +18,5 @@ Device Creation
Physical compression devices are discovered during the bus probe of the EAL function
which is executed at DPDK initialization, based on their unique device identifier.
-For eg. PCI devices can be identified using PCI BDF (bus/bridge, device, function).
+For e.g. PCI devices can be identified using PCI BDF (bus/bridge, device, function).
Specific physical compression devices, like other physical devices in DPDK can be
white-listed or black-listed using the EAL command line options.
@@ -380,5 +380,5 @@ using priv_xform would look like:
}
num_enqd = rte_compressdev_enqueue_burst(cdev_id, 0, comp_ops, NUM_OPS);
- /* wait for this to complete before enqueing next*/
+ /* wait for this to complete before enqueuing next*/
do {
num_deque = rte_compressdev_dequeue_burst(cdev_id, 0 , &processed_ops, NUM_OPS);
@@ -527,5 +527,5 @@ An example pseudocode to set up and process a stream having NUM_CHUNKS with each
op->input_chksum = 0;
num_enqd = rte_compressdev_enqueue_burst(cdev_id, 0, &op[i], 1);
- /* wait for this to complete before enqueing next*/
+ /* wait for this to complete before enqueuing next*/
do {
num_deqd = rte_compressdev_dequeue_burst(cdev_id, 0 , &processed_ops, 1);
diff --git a/doc/guides/prog_guide/cryptodev_lib.rst b/doc/guides/prog_guide/cryptodev_lib.rst
index 8ee33c875..23770ffd4 100644
--- a/doc/guides/prog_guide/cryptodev_lib.rst
+++ b/doc/guides/prog_guide/cryptodev_lib.rst
@@ -15,5 +15,5 @@ Design Principles
-----------------
-The cryptodev library follows the same basic principles as those used in DPDKs
+The cryptodev library follows the same basic principles as those used in DPDK's
Ethernet Device framework. The Crypto framework provides a generic Crypto device
framework which supports both physical (hardware) and virtual (software) Crypto
@@ -49,5 +49,5 @@ From the command line using the --vdev EAL option
number of ``--vdev`` with appropriate libraries are to be added.
- * An Application with crypto PMD instaces sharing the same library requires unique ID.
+ * An Application with crypto PMD instances sharing the same library requires unique ID.
Example: ``--vdev 'crypto_aesni_mb0' --vdev 'crypto_aesni_mb1'``
@@ -383,5 +383,5 @@ Operation Management and Allocation
The cryptodev library provides an API set for managing Crypto operations which
utilize the Mempool Library to allocate operation buffers. Therefore, it ensures
-that the crytpo operation is interleaved optimally across the channels and
+that the crypto operation is interleaved optimally across the channels and
ranks for optimal processing.
A ``rte_crypto_op`` contains a field indicating the pool that it originated from.
@@ -587,5 +587,5 @@ Sample code
There are various sample applications that show how to use the cryptodev library,
such as the L2fwd with Crypto sample application (L2fwd-crypto) and
-the IPSec Security Gateway application (ipsec-secgw).
+the IPsec Security Gateway application (ipsec-secgw).
While these applications demonstrate how an application can be created to perform
@@ -768,5 +768,5 @@ using one of the crypto PMDs available in DPDK.
/*
* Dequeue the crypto operations until all the operations
- * are proccessed in the crypto device.
+ * are processed in the crypto device.
*/
uint16_t num_dequeued_ops, total_num_dequeued_ops = 0;
@@ -847,5 +847,5 @@ Not all asymmetric crypto xforms are supported for chaining. Currently supported
asymmetric crypto chaining is Diffie-Hellman private key generation followed by
public generation. Also, currently API does not support chaining of symmetric and
-asymmetric crypto xfroms.
+asymmetric crypto xforms.
Each xform defines specific asymmetric crypto algo. Currently supported are:
diff --git a/doc/guides/prog_guide/dev_kit_build_system.rst b/doc/guides/prog_guide/dev_kit_build_system.rst
index 002d973a4..a851a8112 100644
--- a/doc/guides/prog_guide/dev_kit_build_system.rst
+++ b/doc/guides/prog_guide/dev_kit_build_system.rst
@@ -248,5 +248,5 @@ Which ``dpdk-pmdinfogen`` scans for. Using this information other relevant
bits of data can be exported from the object file and used to produce a
hardware support description, that ``dpdk-pmdinfogen`` then encodes into a
-json formatted string in the following format:
+JSON formatted string in the following format:
.. code-block:: c
diff --git a/doc/guides/prog_guide/efd_lib.rst b/doc/guides/prog_guide/efd_lib.rst
index cb1a1df86..2b355ff2a 100644
--- a/doc/guides/prog_guide/efd_lib.rst
+++ b/doc/guides/prog_guide/efd_lib.rst
@@ -424,5 +424,5 @@ References
1- EFD is based on collaborative research work between Intel and
Carnegie Mellon University (CMU), interested readers can refer to the paper
-“Scaling Up Clustered Network Appliances with ScaleBricks;” Dong Zhou et al.
+"Scaling Up Clustered Network Appliances with ScaleBricks" Dong Zhou et al.
at SIGCOMM 2015 (`http://conferences.sigcomm.org/sigcomm/2015/pdf/papers/p241.pdf`)
for more information.
diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst
index 888ce7801..94d19682e 100644
--- a/doc/guides/prog_guide/env_abstraction_layer.rst
+++ b/doc/guides/prog_guide/env_abstraction_layer.rst
@@ -649,5 +649,5 @@ The most important fields in the structure and how they are used are described b
Malloc heap is a doubly-linked list, where each element keeps track of its
previous and next elements. Due to the fact that hugepage memory can come and
-go, neighbouring malloc elements may not necessarily be adjacent in memory.
+go, neighboring malloc elements may not necessarily be adjacent in memory.
Also, since a malloc element may span multiple pages, its contents may not
necessarily be IOVA-contiguous either - each malloc element is only guaranteed
diff --git a/doc/guides/prog_guide/event_ethernet_rx_adapter.rst b/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
index 0166bb45d..7bc559c8a 100644
--- a/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
+++ b/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
@@ -158,5 +158,5 @@ is applicable when the adapter uses a service core function. The application
has to enable Rx queue interrupts when configuring the ethernet device
using the ``rte_eth_dev_configure()`` function and then use a servicing_weight
-of zero when addding the Rx queue to the adapter.
+of zero when adding the Rx queue to the adapter.
The adapter creates a thread blocked on the interrupt, on an interrupt this
@@ -176,7 +176,7 @@ For SW based packet transfers, i.e., when the
``RTE_EVENT_ETH_RX_ADAPTER_CAP_INTERNAL_PORT`` is not set in the adapter's
capabilities flags for a particular ethernet device, the service function
-temporarily enqueues mbufs to an event buffer before batch enqueueing these
+temporarily enqueues mbufs to an event buffer before batch enqueuing these
to the event device. If the buffer fills up, the service function stops
-dequeueing packets from the ethernet device. The application may want to
+dequeuing packets from the ethernet device. The application may want to
monitor the buffer fill level and instruct the service function to selectively
enqueue packets to the event device. The application may also use some other
diff --git a/doc/guides/prog_guide/eventdev.rst b/doc/guides/prog_guide/eventdev.rst
index 8fcae5469..27c51d256 100644
--- a/doc/guides/prog_guide/eventdev.rst
+++ b/doc/guides/prog_guide/eventdev.rst
@@ -43,5 +43,5 @@ application fills in to have the event scheduled as required:
* ``flow_id`` - The targeted flow identifier for the enq/deq operation.
-* ``event_type`` - The source of this event, eg RTE_EVENT_TYPE_ETHDEV or CPU.
+* ``event_type`` - The source of this event, e.g. RTE_EVENT_TYPE_ETHDEV or CPU.
* ``sub_event_type`` - Distinguishes events inside the application, that have
the same event_type (see above)
@@ -266,5 +266,5 @@ The final step is to "wire up" the ports to the queues. After this, the
eventdev is capable of scheduling events, and when cores request work to do,
the correct events are provided to that core. Note that the RX core takes input
-from eg: a NIC so it is not linked to any eventdev queues.
+from e.g.: a NIC so it is not linked to any eventdev queues.
Linking all workers to atomic queues, and the TX core to the single-link queue
@@ -277,5 +277,5 @@ can be achieved like this:
uint8_t atomic_qs[] = {0, 1};
uint8_t single_link_q = 2;
- uin8t_t priority = RTE_EVENT_DEV_PRIORITY_NORMAL;
+ uint8_t priority = RTE_EVENT_DEV_PRIORITY_NORMAL;
for(int worker_port_id = 1; worker_port_id <= 4; worker_port_id++) {
diff --git a/doc/guides/prog_guide/kernel_nic_interface.rst b/doc/guides/prog_guide/kernel_nic_interface.rst
index 33ea980e5..7b8a481a6 100644
--- a/doc/guides/prog_guide/kernel_nic_interface.rst
+++ b/doc/guides/prog_guide/kernel_nic_interface.rst
@@ -226,5 +226,5 @@ application functions:
``config_promiscusity``:
- Called when the user changes the promiscusity state of the KNI
+ Called when the user changes the promiscuity state of the KNI
interface. For example, when the user runs ``ip link set promisc
[on|off] dev <ifaceX>``. If the user sets this callback function to
diff --git a/doc/guides/prog_guide/metrics_lib.rst b/doc/guides/prog_guide/metrics_lib.rst
index e68e4e743..89bc7d68f 100644
--- a/doc/guides/prog_guide/metrics_lib.rst
+++ b/doc/guides/prog_guide/metrics_lib.rst
@@ -26,5 +26,5 @@ restriction on port numbers is that they are less than ``RTE_MAX_ETHPORTS``
- there is no requirement for the ports to actually exist.
-Initialising the library
+Initializing the library
------------------------
diff --git a/doc/guides/prog_guide/multi_proc_support.rst b/doc/guides/prog_guide/multi_proc_support.rst
index 1384fe335..6196d3f21 100644
--- a/doc/guides/prog_guide/multi_proc_support.rst
+++ b/doc/guides/prog_guide/multi_proc_support.rst
@@ -274,5 +274,5 @@ will be populated by IPC are as follows:
replied)
* ``msgs`` - pointer to where all of the responses are stored. The order in
- which responses appear is undefined. Whendoing sycnrhonous requests, this
+ which responses appear is undefined. When doing synchronous requests, this
memory must be freed by the requestor after request completes!
diff --git a/doc/guides/prog_guide/profile_app.rst b/doc/guides/prog_guide/profile_app.rst
index 02f05614a..c1b29f937 100644
--- a/doc/guides/prog_guide/profile_app.rst
+++ b/doc/guides/prog_guide/profile_app.rst
@@ -65,5 +65,5 @@ get a wall clock counter in user space. Typically it runs at <= 100MHz.
The alternative method to enable ``rte_rdtsc()`` for a high resolution wall
-clock counter is through the armv8 PMU subsystem. The PMU cycle counter runs
+clock counter is through the ARMv8 PMU subsystem. The PMU cycle counter runs
at CPU frequency. However, access to the PMU cycle counter from user space is
not enabled by default in the arm64 linux kernel. It is possible to enable
@@ -76,5 +76,5 @@ scheme. Application can choose the PMU based implementation with
The example below shows the steps to configure the PMU based cycle counter on
-an armv8 machine.
+an ARMv8 machine.
.. code-block:: console
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index dbf4999aa..4e9b4440b 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -2132,5 +2132,5 @@ as defined in the ``rte_flow_action_raw_decap``
This action modifies the payload of matched flows. The data supplied must
be a valid header, either holding layer 2 data in case of removing layer 2
-before eincapsulation of layer 3 tunnel (for example MPLSoGRE) or complete
+before encapsulation of layer 3 tunnel (for example MPLSoGRE) or complete
tunnel definition starting from layer 2 and moving to the tunnel item itself.
When applied to the original packet the resulting packet must be a
@@ -2282,5 +2282,5 @@ Decrease TTL value.
If there is no valid RTE_FLOW_ITEM_TYPE_IPV4 or RTE_FLOW_ITEM_TYPE_IPV6
-in pattern, Some PMDs will reject rule because behaviour will be undefined.
+in pattern, Some PMDs will reject rule because behavior will be undefined.
.. _table_rte_flow_action_dec_ttl:
@@ -2300,5 +2300,5 @@ Assigns a new TTL value.
If there is no valid RTE_FLOW_ITEM_TYPE_IPV4 or RTE_FLOW_ITEM_TYPE_IPV6
-in pattern, Some PMDs will reject rule because behaviour will be undefined.
+in pattern, Some PMDs will reject rule because behavior will be undefined.
.. _table_rte_flow_action_set_ttl:
@@ -2726,5 +2726,5 @@ Caveats
returned).
-- There is no provision for reentrancy/multi-thread safety, although nothing
+- There is no provision for re-entrancy/multi-thread safety, although nothing
should prevent different devices from being configured at the same
time. PMDs may protect their control path functions accordingly.
diff --git a/doc/guides/prog_guide/rte_security.rst b/doc/guides/prog_guide/rte_security.rst
index cb70caa74..7d0734a37 100644
--- a/doc/guides/prog_guide/rte_security.rst
+++ b/doc/guides/prog_guide/rte_security.rst
@@ -41,5 +41,5 @@ Inline Crypto
RTE_SECURITY_ACTION_TYPE_INLINE_CRYPTO:
-The crypto processing for security protocol (e.g. IPSec) is processed
+The crypto processing for security protocol (e.g. IPsec) is processed
inline during receive and transmission on NIC port. The flow based
security action should be configured on the port.
@@ -49,5 +49,5 @@ crypto status is set in Rx descriptors. After the successful inline
crypto processing the packet is presented to host as a regular Rx packet
however all security protocol related headers are still attached to the
-packet. e.g. In case of IPSec, the IPSec tunnel headers (if any),
+packet. e.g. In case of IPsec, the IPsec tunnel headers (if any),
ESP/AH headers will remain in the packet but the received packet
contains the decrypted data where the encrypted data was when the packet
@@ -112,5 +112,5 @@ Inline protocol offload
RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL:
-The crypto and protocol processing for security protocol (e.g. IPSec)
+The crypto and protocol processing for security protocol (e.g. IPsec)
is processed inline during receive and transmission. The flow based
security action should be configured on the port.
@@ -120,5 +120,5 @@ crypto status is set in the Rx descriptors. After the successful inline
crypto processing the packet is presented to the host as a regular Rx packet
but all security protocol related headers are optionally removed from the
-packet. e.g. in the case of IPSec, the IPSec tunnel headers (if any),
+packet. e.g. in the case of IPsec, the IPsec tunnel headers (if any),
ESP/AH headers will be removed from the packet and the received packet
will contains the decrypted packet only. The driver Rx path checks the
@@ -133,5 +133,5 @@ to identify the security processing done on the packet.
the device shall support crypto processing for all kind of packets matching
to a given flow, this includes fragmented packets (post reassembly).
- E.g. in case of IPSec the device may internally manage anti-replay etc.
+ E.g. in case of IPsec the device may internally manage anti-replay etc.
It will provide a configuration option for anti-replay behavior i.e. to drop
the packets or pass them to driver with error flags set in the descriptor.
@@ -151,5 +151,5 @@ to cross the MTU size.
The underlying device will manage state information required for egress
- processing. E.g. in case of IPSec, the seq number will be added to the
+ processing. E.g. in case of IPsec, the seq number will be added to the
packet, however the device shall provide indication when the sequence number
is about to overflow. The underlying device may support post encryption TSO.
@@ -200,5 +200,5 @@ Decryption: The packet is sent to the crypto device for security
protocol processing. The device will decrypt the packet and it will also
optionally remove additional security headers from the packet.
-E.g. in case of IPSec, IPSec tunnel headers (if any), ESP/AH headers
+E.g. in case of IPsec, IPsec tunnel headers (if any), ESP/AH headers
will be removed from the packet and the decrypted packet may contain
plain data only.
@@ -206,5 +206,5 @@ plain data only.
.. note::
- In case of IPSec the device may internally manage anti-replay etc.
+ In case of IPsec the device may internally manage anti-replay etc.
It will provide a configuration option for anti-replay behavior i.e. to drop
the packets or pass them to driver with error flags set in descriptor.
@@ -218,5 +218,5 @@ for any protocol header addition.
.. note::
- In the case of IPSec, the seq number will be added to the packet,
+ In the case of IPsec, the seq number will be added to the packet,
It shall provide an indication when the sequence number is about to
overflow.
@@ -550,5 +550,5 @@ IPsec related configuration parameters are defined in ``rte_security_ipsec_xform
/**< various SA options */
enum rte_security_ipsec_sa_direction direction;
- /**< IPSec SA Direction - Egress/Ingress */
+ /**< IPsec SA Direction - Egress/Ingress */
enum rte_security_ipsec_sa_protocol proto;
/**< IPsec SA Protocol - AH/ESP */
diff --git a/doc/guides/prog_guide/traffic_management.rst b/doc/guides/prog_guide/traffic_management.rst
index 98ac4310b..05b34d93a 100644
--- a/doc/guides/prog_guide/traffic_management.rst
+++ b/doc/guides/prog_guide/traffic_management.rst
@@ -40,5 +40,5 @@ At the TM level, users can get high level idea with the help of various
parameters such as maximum number of nodes, maximum number of hierarchical
levels, maximum number of shapers, maximum number of private shapers, type of
-scheduling algorithm (Strict Priority, Weighted Fair Queueing , etc.), etc.,
+scheduling algorithm (Strict Priority, Weighted Fair Queuing , etc.), etc.,
supported by the implementation.
diff --git a/doc/guides/prog_guide/vhost_lib.rst b/doc/guides/prog_guide/vhost_lib.rst
index c77df338f..27c3af8f9 100644
--- a/doc/guides/prog_guide/vhost_lib.rst
+++ b/doc/guides/prog_guide/vhost_lib.rst
@@ -64,5 +64,5 @@ The following is an overview of some key Vhost API functions:
* zero copy is really good for VM2VM case. For iperf between two VMs, the
- boost could be above 70% (when TSO is enableld).
+ boost could be above 70% (when TSO is enabled).
* For zero copy in VM2NIC case, guest Tx used vring may be starved if the
diff --git a/doc/guides/rawdevs/ifpga_rawdev.rst b/doc/guides/rawdevs/ifpga_rawdev.rst
index d400db6ed..a3d92a62e 100644
--- a/doc/guides/rawdevs/ifpga_rawdev.rst
+++ b/doc/guides/rawdevs/ifpga_rawdev.rst
@@ -92,5 +92,5 @@ Run-time parameters
This driver is invoked automatically in systems added with Intel FPGA,
-but PR and IFPGA Bus scan is trigged by command line using
+but PR and IFPGA Bus scan is triggered by command line using
``--vdev 'ifpga_rawdev_cfg`` EAL option.
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 358dfa321..276327c15 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -677,5 +677,5 @@ igb uio legacy mode can not be used in X710/XL710/XXV710
**Description**:
X710/XL710/XXV710 NICs lack support for indicating INTx is asserted via the interrupt
- bit in the PCI status register. Linux delected them from INTx support table. The related
+ bit in the PCI status register. Linux deleted them from INTx support table. The related
`commit <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/drivers/pci/quirks.c?id=8bcf4525c5d43306c5fd07e132bc8650e3491aec>`_.
@@ -723,7 +723,7 @@ Linux kernel 4.10.0 iommu attribute read error
When VT-d is enabled (``iommu=pt intel_iommu=on``), reading IOMMU attributes from
/sys/devices/virtual/iommu/dmarXXX/intel-iommu/cap on Linux kernel 4.10.0 error.
- This bug is fixed in `Linux commmit a7fdb6e648fb
+ This bug is fixed in `Linux commit a7fdb6e648fb
<https://patchwork.kernel.org/patch/9595727/>`_,
- This bug is introduced in `Linux commmit 39ab9555c241
+ This bug is introduced in `Linux commit 39ab9555c241
<https://patchwork.kernel.org/patch/9554403/>`_,
@@ -843,5 +843,5 @@ AVX-512 support disabled
On DPDK v19.02 ``AVX-512`` disable scope is reduced to ``GCC`` and ``binutils version 2.30`` based
- on information accured from the GCC community defect.
+ on information accrued from the GCC community defect.
**Reason**:
diff --git a/doc/guides/rel_notes/release_17_11.rst b/doc/guides/rel_notes/release_17_11.rst
index 2a93af323..6448b6cb1 100644
--- a/doc/guides/rel_notes/release_17_11.rst
+++ b/doc/guides/rel_notes/release_17_11.rst
@@ -169,5 +169,5 @@ New Features
* The DES DOCSIS BPI algorithm.
- This change requires version 0.47 of the IPSec Multi-buffer library. For
+ This change requires version 0.47 of the IPsec Multi-buffer library. For
more details see the :doc:`../cryptodevs/aesni_mb` documentation.
@@ -199,5 +199,5 @@ New Features
Added an experimental library - ``rte_security``. This provide security APIs
- for protocols like IPSec using inline ipsec offload to ethernet devices or
+ for protocols like IPsec using inline ipsec offload to ethernet devices or
full protocol offload with lookaside crypto devices.
@@ -208,9 +208,9 @@ New Features
Updated the ``dpaa2_sec`` crypto PMD to support ``rte_security`` lookaside
- protocol offload for IPSec.
+ protocol offload for IPsec.
* **Updated the IXGBE ethernet driver to support rte_security.**
- Updated ixgbe ethernet PMD to support ``rte_security`` inline IPSec offload.
+ Updated ixgbe ethernet PMD to support ``rte_security`` inline IPsec offload.
* **Updated i40e driver to support GTP-C/GTP-U.**
@@ -510,5 +510,5 @@ ABI Changes
A new parameter ``security_ctx`` has been added to ``rte_eth_dev`` to
- support security operations like IPSec inline.
+ support security operations like IPsec inline.
* **New parameter added to rte_cryptodev.**
diff --git a/doc/guides/sample_app_ug/bbdev_app.rst b/doc/guides/sample_app_ug/bbdev_app.rst
index 653f972f3..6ade9c6e1 100644
--- a/doc/guides/sample_app_ug/bbdev_app.rst
+++ b/doc/guides/sample_app_ug/bbdev_app.rst
@@ -69,5 +69,5 @@ The application accepts a number of command line options:
where:
-* ``e ENCODING_CORES``: hexmask for encoding lcored (default = 0x2)
+* ``e ENCODING_CORES``: hexmask for encoding lcores (default = 0x2)
* ``d DECODING_CORES``: hexmask for decoding lcores (default = 0x4)
* ``p ETH_PORT_ID``: ethernet port ID (default = 0)
@@ -88,5 +88,5 @@ issue the command:
--file-prefix=bbdev -- -e 0x10 -d 0x20
-where, NIC0PCIADDR is the PCI addresse of the Rx port
+where, NIC0PCIADDR is the PCI address of the Rx port
This command creates one virtual bbdev devices ``baseband_turbo_sw`` where the
diff --git a/doc/guides/sample_app_ug/eventdev_pipeline.rst b/doc/guides/sample_app_ug/eventdev_pipeline.rst
index 0ec02907d..dc7972aa9 100644
--- a/doc/guides/sample_app_ug/eventdev_pipeline.rst
+++ b/doc/guides/sample_app_ug/eventdev_pipeline.rst
@@ -50,5 +50,5 @@ these settings is shown below:
The application has some sanity checking built-in, so if there is a function
-(eg; the RX core) which doesn't have a cpu core mask assigned, the application
+(e.g.; the RX core) which doesn't have a cpu core mask assigned, the application
will print an error message:
diff --git a/doc/guides/sample_app_ug/intro.rst b/doc/guides/sample_app_ug/intro.rst
index 159bcf73b..90704194a 100644
--- a/doc/guides/sample_app_ug/intro.rst
+++ b/doc/guides/sample_app_ug/intro.rst
@@ -107,5 +107,5 @@ examples are highlighted below.
and TX packet processing functions.
-* :doc:`IPSec Security Gateway<ipsec_secgw>`: The IPSec Security
+* :doc:`IPsec Security Gateway<ipsec_secgw>`: The IPsec Security
Gateway application is minimal example of something closer to a real world
example. This is also a good example of an application using the DPDK
diff --git a/doc/guides/sample_app_ug/ip_pipeline.rst b/doc/guides/sample_app_ug/ip_pipeline.rst
index 447a544d5..4da0fcf89 100644
--- a/doc/guides/sample_app_ug/ip_pipeline.rst
+++ b/doc/guides/sample_app_ug/ip_pipeline.rst
@@ -114,5 +114,5 @@ Initialization
~~~~~~~~~~~~~~
-During this stage, EAL layer is initialised and application specific arguments are parsed. Furthermore, the data strcutures
+During this stage, EAL layer is initialised and application specific arguments are parsed. Furthermore, the data structures
(i.e. linked lists) for application objects are initialized. In case of any initialization error, an error message
is displayed and the application is terminated.
@@ -186,5 +186,5 @@ Examples
| IP routing | LPM (IPv4) | Forward | 1. Mempool Create |
| | | | 2. Link create |
- | | * Key = IP dest addr | | 3. Pipeline creat |
+ | | * Key = IP dest addr | | 3. Pipeline create |
| | * Offset = 286 | | 4. Pipeline port in/out |
| | * Table size = 4K | | 5. Pipeline table |
diff --git a/doc/guides/sample_app_ug/ipsec_secgw.rst b/doc/guides/sample_app_ug/ipsec_secgw.rst
index 4869a011d..5f7d39736 100644
--- a/doc/guides/sample_app_ug/ipsec_secgw.rst
+++ b/doc/guides/sample_app_ug/ipsec_secgw.rst
@@ -26,6 +26,6 @@ Thus, traffic received on an Unprotected or Protected port is consider
Inbound or Outbound respectively.
-The application also supports complete IPSec protocol offload to hardware
-(Look aside crypto accelarator or using ethernet device). It also support
+The application also supports complete IPsec protocol offload to hardware
+(Look aside crypto accelerator or using ethernet device). It also support
inline ipsec processing by the supported ethernet device during transmission.
These modes can be selected during the SA creation configuration.
diff --git a/doc/guides/sample_app_ug/performance_thread.rst b/doc/guides/sample_app_ug/performance_thread.rst
index fbd30a5ea..96f0fc6fd 100644
--- a/doc/guides/sample_app_ug/performance_thread.rst
+++ b/doc/guides/sample_app_ug/performance_thread.rst
@@ -501,6 +501,6 @@ the L-thread struct.
For legacy and backward compatibility reasons two alternative methods are also
-offered, the first is modelled directly on the pthread get/set specific APIs,
-the second approach is modelled on the ``RTE_PER_LCORE`` macros, whereby
+offered, the first is modeled directly on the pthread get/set specific APIs,
+the second approach is modeled on the ``RTE_PER_LCORE`` macros, whereby
``PER_LTHREAD`` macros are introduced, in both cases the storage is local to
the L-thread.
diff --git a/doc/guides/sample_app_ug/qos_metering.rst b/doc/guides/sample_app_ug/qos_metering.rst
index 2e8e0175f..d75f7da52 100644
--- a/doc/guides/sample_app_ug/qos_metering.rst
+++ b/doc/guides/sample_app_ug/qos_metering.rst
@@ -152,4 +152,4 @@ In this particular case:
.. note::
- * In color blind mode, first row GREEN colour is only valid.
+ * In color blind mode, first row GREEN color is only valid.
* To drop the packet, policer_table action has to be set to DROP.
diff --git a/doc/guides/sample_app_ug/test_pipeline.rst b/doc/guides/sample_app_ug/test_pipeline.rst
index a9370c80b..af9665b2c 100644
--- a/doc/guides/sample_app_ug/test_pipeline.rst
+++ b/doc/guides/sample_app_ug/test_pipeline.rst
@@ -33,5 +33,5 @@ Compiling the Application
To compile the sample application see :doc:`compiling`
-The application is located in the ``$RTE_SDK/test/test-pipline`` directory.
+The application is located in the ``$RTE_SDK/test/test-pipeline`` directory.
diff --git a/doc/guides/sample_app_ug/vhost.rst b/doc/guides/sample_app_ug/vhost.rst
index df4d6f9a0..a71ada654 100644
--- a/doc/guides/sample_app_ug/vhost.rst
+++ b/doc/guides/sample_app_ug/vhost.rst
@@ -117,5 +117,5 @@ The vm2vm parameter sets the mode of packet switching between guests in
the host.
-- 0 disables vm2vm, impling that VM's packets will always go to the NIC port.
+- 0 disables vm2vm, implying that VM's packets will always go to the NIC port.
- 1 means a normal mac lookup packet routing.
- 2 means hardware mode packet forwarding between guests, it allows packets
@@ -149,5 +149,5 @@ default value is 15.
**--dequeue-zero-copy**
Dequeue zero copy will be enabled when this option is given. it is worth to
-note that if NIC is binded to driver with iommu enabled, dequeue zero copy
+note that if NIC is bound to driver with iommu enabled, dequeue zero copy
cannot work at VM2NIC mode (vm2vm=0) due to currently we don't setup iommu
dma mapping for guest memory.
diff --git a/doc/guides/sample_app_ug/vhost_scsi.rst b/doc/guides/sample_app_ug/vhost_scsi.rst
index 7ab7d0d53..6b9bf62eb 100644
--- a/doc/guides/sample_app_ug/vhost_scsi.rst
+++ b/doc/guides/sample_app_ug/vhost_scsi.rst
@@ -64,5 +64,5 @@ Vhost_scsi Common Issues
* vhost_scsi can not start with block size 512 Bytes:
- Currently DPDK vhost library was designed for NET device(althrough the APIs
+ Currently DPDK vhost library was designed for NET device(although the APIs
are generic now), for 512 Bytes block device, Qemu BIOS(x86 BIOS Enhanced
Disk Device) will enumerate all block device and do some IOs to those block
diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst
index 5be9f24d5..57758ca00 100644
--- a/doc/guides/sample_app_ug/vm_power_management.rst
+++ b/doc/guides/sample_app_ug/vm_power_management.rst
@@ -340,5 +340,5 @@ monitoring of branch ratio on cores doing busy polling via PMDs.
When this parameter is used, the list of cores specified will monitor the ratio
between branch hits and branch misses. A tightly polling PMD thread will have a
- very low branch ratio, so the core frequency will be scaled down to the minimim
+ very low branch ratio, so the core frequency will be scaled down to the minimum
allowed value. When packets are received, the code path will alter, causing the
branch ratio to increase. When the ratio goes above the ratio threshold, the
@@ -380,5 +380,5 @@ the file.
The fifo is at /tmp/powermonitor/fifo
-The jason string can be a policy or instruction, and takes the following
+The JSON string can be a policy or instruction, and takes the following
format:
@@ -730,5 +730,5 @@ policy down to the host application. These parameters are as follows:
monitor. The list of cores in any vm starts at zero, and these are mapped to the
physical cores by the host application once the policy is passed down.
- Valid syntax includes individial cores '2,3,4', or a range of cores '2-4', or a
+ Valid syntax includes individual cores '2,3,4', or a range of cores '2-4', or a
combination of both '1,3,5-7'
@@ -738,5 +738,5 @@ policy down to the host application. These parameters are as follows:
A comma-separated list of hours within which to set the core frequency to maximum.
- Valid syntax includes individial hours '2,3,4', or a range of hours '2-4', or a
+ Valid syntax includes individual hours '2,3,4', or a range of hours '2-4', or a
combination of both '1,3,5-7'. Valid hours are 0 to 23.
@@ -746,5 +746,5 @@ policy down to the host application. These parameters are as follows:
A comma-separated list of hours within which to set the core frequency to minimum.
- Valid syntax includes individial hours '2,3,4', or a range of hours '2-4', or a
+ Valid syntax includes individual hours '2,3,4', or a range of hours '2-4', or a
combination of both '1,3,5-7'. Valid hours are 0 to 23.
diff --git a/doc/guides/testpmd_app_ug/run_app.rst b/doc/guides/testpmd_app_ug/run_app.rst
index e934b4bed..89df03166 100644
--- a/doc/guides/testpmd_app_ug/run_app.rst
+++ b/doc/guides/testpmd_app_ug/run_app.rst
@@ -366,5 +366,5 @@ The command line options are:
* ``--hot-plug``
- Enable device event monitor mechanism for hot plug.
+ Enable device event monitor mechanism for hotplug.
* ``--vxlan-gpe-port=N``
@@ -406,5 +406,5 @@ The command line options are:
* ``--noisy-lkup-memory=N``
- Set the size of the noisy neighbour simulation memory buffer in MB to N.
+ Set the size of the noisy neighbor simulation memory buffer in MB to N.
Only available with the noisy forwarding mode. The default value is 0.
@@ -412,14 +412,14 @@ The command line options are:
* ``--noisy-lkup-num-reads=N``
- Set the number of reads to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of reads to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-writes=N``
- Set the number of writes to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of writes to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-reads-writes=N``
- Set the number of r/w accesses to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of r/w accesses to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
index d4e3fd8a5..34f7bc766 100644
--- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
+++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
@@ -303,5 +303,5 @@ The available information categories are:
* ``mac``: Changes the source and the destination Ethernet addresses of packets before forwarding them.
- Default application behaviour is to set source Ethernet address to that of the transmitting interface, and destination
+ Default application behavior is to set source Ethernet address to that of the transmitting interface, and destination
address to a dummy value (set during init). The user may specify a target destination Ethernet address via the 'eth-peer' or
'eth-peers-configfile' command-line options. It is not currently possible to specify a specific source Ethernet address.
@@ -326,5 +326,5 @@ The available information categories are:
similar to I/O mode except for the fact that packets are loopback to the softnic ports only. Therefore, portmask parameter should be set to softnic port only. The various software based custom NIC pipelines specified through the softnic firmware (DPDK packet framework script) can be tested in this mode. Furthermore, it allows to build 5-level hierarchical QoS scheduler as a default option that can be enabled through CLI once testpmd application is initialised. The user can modify the default scheduler hierarchy or can specify the new QoS Scheduler hierarchy through CLI. Requires ``CONFIG_RTE_LIBRTE_PMD_SOFTNIC=y``.
-* ``noisy``: Noisy neighbour simulation.
+* ``noisy``: Noisy neighbor simulation.
Simulate more realistic behavior of a guest machine engaged in receiving
and sending packets performing Virtual Network Function (VNF).
@@ -2247,5 +2247,5 @@ set bonding lacp dedicated_queue
Enable dedicated tx/rx queues on bonding devices slaves to handle LACP control plane traffic
-when in mode 4 (link-aggregration-802.3ad)::
+when in mode 4 (link-aggregation-802.3ad)::
testpmd> set bonding lacp dedicated_queues (port_id) (enable|disable)
@@ -2255,5 +2255,5 @@ set bonding agg_mode
~~~~~~~~~~~~~~~~~~~~
-Enable one of the specific aggregators mode when in mode 4 (link-aggregration-802.3ad)::
+Enable one of the specific aggregators mode when in mode 4 (link-aggregation-802.3ad)::
testpmd> set bonding agg_mode (port_id) (bandwidth|count|stable)
@@ -2649,6 +2649,6 @@ where:
* ``shared_shaper_id``: Shared shaper ID to be deleted.
-Set port traffic management hiearchy node private shaper
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Set port traffic management hierarchy node private shaper
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
set the port traffic management hierarchy node private shaper::
@@ -2701,5 +2701,5 @@ Add port traffic management hierarchy nonleaf node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Add nonleaf node to port traffic management hiearchy::
+Add nonleaf node to port traffic management hierarchy::
testpmd> add port tm nonleaf node (port_id) (node_id) (parent_node_id) \
@@ -2716,5 +2716,5 @@ where:
to the weight sum of all siblings that have the same priority. It is used by
the WFQ algorithm running on the parent node for scheduling this node.
-* ``level_id``: Hiearchy level of the node.
+* ``level_id``: Hierarchy level of the node.
* ``shaper_profile_id``: Shaper profile ID of the private shaper to be used by
the node.
@@ -2727,5 +2727,5 @@ Add port traffic management hierarchy leaf node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Add leaf node to port traffic management hiearchy::
+Add leaf node to port traffic management hierarchy::
testpmd> add port tm leaf node (port_id) (node_id) (parent_node_id) \
@@ -2742,5 +2742,5 @@ where:
to the weight sum of all siblings that have the same priority. It is used by
the WFQ algorithm running on the parent node for scheduling this node.
-* ``level_id``: Hiearchy level of the node.
+* ``level_id``: Hierarchy level of the node.
* ``shaper_profile_id``: Shaper profile ID of the private shaper to be used by
the node.
@@ -2754,5 +2754,5 @@ Delete port traffic management hierarchy node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Delete node from port traffic management hiearchy::
+Delete node from port traffic management hierarchy::
testpmd> del port tm node (port_id) (node_id)
@@ -3947,5 +3947,5 @@ This section lists supported actions and their attributes, if any.
- ``dec_ttl``: Performs a decrease TTL value action
-- ``set_ttl``: Set TTL value with specificed value
+- ``set_ttl``: Set TTL value with specified value
- ``ttl_value {unsigned}``: The new TTL value to be set
@@ -4468,5 +4468,5 @@ bpf-load
~~~~~~~~
-Load an eBPF program as a callback for partciular RX/TX queue::
+Load an eBPF program as a callback for particular RX/TX queue::
testpmd> bpf-load rx|tx (portid) (queueid) (load-flags) (bpf-prog-filename)
@@ -4506,5 +4506,5 @@ bpf-unload
~~~~~~~~~~
-Unload previously loaded eBPF program for partciular RX/TX queue::
+Unload previously loaded eBPF program for particular RX/TX queue::
testpmd> bpf-unload rx|tx (portid) (queueid)
diff --git a/doc/guides/tools/cryptoperf.rst b/doc/guides/tools/cryptoperf.rst
index c366af4e9..2fc65441d 100644
--- a/doc/guides/tools/cryptoperf.rst
+++ b/doc/guides/tools/cryptoperf.rst
@@ -60,5 +60,5 @@ To set on the linearization options add below definition to the
Execute the ``dpdk-setup.sh`` script to build the DPDK library together with the
-``dpdk-test-crypto-perf`` applcation.
+``dpdk-test-crypto-perf`` application.
Initially, the user must select a DPDK target to choose the correct target type
@@ -81,5 +81,5 @@ EAL Options
The following are the EAL command-line options that can be used in conjunction
-with the ``dpdk-test-crypto-perf`` applcation.
+with the ``dpdk-test-crypto-perf`` application.
See the DPDK Getting Started Guides for more information on these options.
@@ -97,8 +97,8 @@ See the DPDK Getting Started Guides for more information on these options.
Add a virtual device.
-Appication Options
-~~~~~~~~~~~~~~~~~~
+Application Options
+~~~~~~~~~~~~~~~~~~~
-The following are the appication command-line options:
+The following are the application command-line options:
* ``--ptest type``
@@ -339,5 +339,5 @@ The test vector file is a text file contain information about test vectors.
The file is made of the sections. The first section doesn't have header.
It contain global information used in each test variant vectors -
-typically information about plaintext, ciphertext, cipher key, aut key,
+typically information about plaintext, ciphertext, cipher key, auth key,
initial vector. All other sections begin header.
The sections contain particular information typically digest.
@@ -345,5 +345,5 @@ The sections contain particular information typically digest.
**Format of the file:**
-Each line beginig with sign '#' contain comment and it is ignored by parser::
+Each line beginning with sign '#' contain comment and it is ignored by parser::
# <comment>
@@ -353,14 +353,14 @@ Header line is just name in square bracket::
[<section name>]
-Data line contain information tocken then sign '=' and
+Data line contain information token then sign '=' and
a string of bytes in C byte array format::
- <tocken> = <C byte array>
+ <token> = <C byte array>
-**Tockens list:**
+**Tokens list:**
* ``plaintext``
- Original plaintext to be crypted.
+ Original plaintext to be encrypted.
* ``ciphertext``
diff --git a/doc/guides/tools/proc_info.rst b/doc/guides/tools/proc_info.rst
index d5b5ed6a6..e9a0b79d3 100644
--- a/doc/guides/tools/proc_info.rst
+++ b/doc/guides/tools/proc_info.rst
@@ -49,5 +49,5 @@ Limitations
* When running ``dpdk-procinfo`` with shared library mode, it is required to
pass the same NIC PMD libraries as used for the primary application. Any
- mismatch in PMD library arguments can lead to undefined behaviour and results
+ mismatch in PMD library arguments can lead to undefined behavior and results
affecting primary application too.
diff --git a/doc/guides/tools/testbbdev.rst b/doc/guides/tools/testbbdev.rst
index af38b1632..a8cb6fbbe 100644
--- a/doc/guides/tools/testbbdev.rst
+++ b/doc/guides/tools/testbbdev.rst
@@ -140,5 +140,5 @@ There are 6 main test cases that can be executed using testbbdev tool:
- Measures the time consumed from the first enqueue until the first
appearance of a dequeued result
- - This measurment represents the full latency of a bbdev operation
+ - This measurement represents the full latency of a bbdev operation
(encode or decode) to execute
--
2.20.1
---
Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- - 2019-05-08 16:33:57.582103233 +0100
+++ 0003-doc-fix-spelling-reported-by-aspell-in-guides.patch 2019-05-08 16:33:57.316581212 +0100
@@ -1 +1 @@
-From d629b7b5fe812f0040b83d27d2ada33b003aa918 Mon Sep 17 00:00:00 2001
+From 8ca6a5b8794806d131f4bd3faf776894d8ecd90a Mon Sep 17 00:00:00 2001
@@ -5,0 +6,2 @@
+[ upstream commit d629b7b5fe812f0040b83d27d2ada33b003aa918 ]
+
@@ -22 +23,0 @@
- doc/guides/nics/af_packet.rst | 4 +--
@@ -27 +27,0 @@
- doc/guides/nics/ena.rst | 2 +-
@@ -34,2 +34 @@
- doc/guides/nics/mlx4.rst | 2 +-
- doc/guides/nics/mlx5.rst | 4 +--
+ doc/guides/nics/mlx5.rst | 2 +-
@@ -38,2 +36,0 @@
- doc/guides/nics/nfb.rst | 2 +-
- doc/guides/nics/nfp.rst | 4 +--
@@ -53 +49,0 @@
- doc/guides/prog_guide/ipsec_lib.rst | 16 +++++------
@@ -69 +65 @@
- doc/guides/sample_app_ug/ipsec_secgw.rst | 8 +++---
+ doc/guides/sample_app_ug/ipsec_secgw.rst | 4 +--
@@ -79 +75 @@
- doc/guides/tools/proc_info.rst | 6 ++--
+ doc/guides/tools/proc_info.rst | 2 +-
@@ -81 +77 @@
- 70 files changed, 169 insertions(+), 169 deletions(-)
+ 64 files changed, 149 insertions(+), 149 deletions(-)
@@ -95 +91 @@
-index d8404e623..3b2b174ad 100644
+index a64bb0368..427137dc7 100644
@@ -106 +102 @@
-index 89152010a..1eff2b073 100644
+index d9fd41ae5..ccfc137f1 100644
@@ -109 +105 @@
-@@ -130,5 +130,5 @@ For AES Counter mode (AES-CTR), the library supports two different sizes for Ini
+@@ -126,5 +126,5 @@ For AES Counter mode (AES-CTR), the library supports two different sizes for Ini
@@ -117 +113 @@
-index 12f342b0f..a972c794f 100644
+index 407f063de..f9f8c7bec 100644
@@ -168 +164 @@
-index ee8ccdaf5..07563b3e2 100644
+index a47d6dbf8..4e5ef4d56 100644
@@ -179 +175 @@
-index 6ebc10f71..ecb783290 100644
+index 3f5ebd58a..019c124d4 100644
@@ -197 +193 @@
-index 3dcda6cb1..e197376e2 100644
+index 6a8534d98..e080570e9 100644
@@ -253,18 +248,0 @@
-diff --git a/doc/guides/nics/af_packet.rst b/doc/guides/nics/af_packet.rst
-index 1260bb2c6..efd6f1ca7 100644
---- a/doc/guides/nics/af_packet.rst
-+++ b/doc/guides/nics/af_packet.rst
-@@ -14,5 +14,5 @@ and kernel, that's used to send and receive packets. This helps reducing system
- calls and the copies needed between user space and Kernel.
-
--The PACKET_FANOUT_HASH behaviour of AF_PACKET is used for frame reception.
-+The PACKET_FANOUT_HASH behavior of AF_PACKET is used for frame reception.
-
- Options and inherent limitations
-@@ -20,5 +20,5 @@ Options and inherent limitations
-
- The following options can be provided to set up an af_packet port in DPDK.
--Some of these, in turn, will be used to configure the PAKET_MMAP settings.
-+Some of these, in turn, will be used to configure the PACKET_MMAP settings.
-
- * ``iface`` - name of the Kernel interface to attach to (required);
@@ -272 +250 @@
-index 22f2410d0..3f3f2949f 100644
+index 80591b13c..f6f2c66bf 100644
@@ -280 +257,0 @@
- - MACSEC offload
@@ -281,0 +259 @@
+ Configuration Information
@@ -283 +261 @@
-index f3e611506..7a893cc1d 100644
+index 58d88eef5..39106274e 100644
@@ -301 +279 @@
-index cd35cabde..f85920012 100644
+index 2173673b9..5900ed0df 100644
@@ -310 +288 @@
- Currently these queues are not used for LS1023/LS1043 platform by default.
+
@@ -312 +290 @@
-index 10b9d7dff..a698e5ab6 100644
+index 769dc4e12..04370e4cd 100644
@@ -322,11 +299,0 @@
-diff --git a/doc/guides/nics/ena.rst b/doc/guides/nics/ena.rst
-index 80da4b6be..d44f3cd5c 100644
---- a/doc/guides/nics/ena.rst
-+++ b/doc/guides/nics/ena.rst
-@@ -190,5 +190,5 @@ Prerequisites
- the PCI to the device, before the DMA is even triggered. For proper work
- kernel PCI driver must support write combining (WC). In mainline version of
-- ``igb_uio`` (in DPDK repo) it must be enabled by loding module with
-+ ``igb_uio`` (in DPDK repo) it must be enabled by loading module with
- ``wc_activate=1`` flag (example below). However, mainline's vfio-pci
- driver in kernel doesn't have WC support yet (planed to be added).
@@ -334 +301 @@
-index 26204601a..3c896eeff 100644
+index 8038bf205..376768d39 100644
@@ -337 +304 @@
-@@ -77,5 +77,5 @@ Prerequisites
+@@ -70,5 +70,5 @@ Prerequisites
@@ -345 +312 @@
-index 726a69e93..cdb55e037 100644
+index 3b45b3b3f..c1b83b9b6 100644
@@ -367 +334 @@
-index 9680a92a9..2e9ec799e 100644
+index 40bf0f140..62e90d9fd 100644
@@ -370 +337 @@
-@@ -581,5 +581,5 @@ TC TX scheduling mode setting
+@@ -572,5 +572,5 @@ TC TX scheduling mode setting
@@ -391 +358 @@
-index a66c59531..602a06b5f 100644
+index 204fbd563..c4fc96373 100644
@@ -394 +361 @@
-@@ -66,5 +66,5 @@ PMD arguments
+@@ -65,5 +65,5 @@ PMD arguments
@@ -401,11 +367,0 @@
-diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst
-index aaf190753..f6d7a16e4 100644
---- a/doc/guides/nics/mlx4.rst
-+++ b/doc/guides/nics/mlx4.rst
-@@ -84,5 +84,5 @@ These options can be modified in the ``.config`` file.
- - ``CONFIG_RTE_IBVERBS_LINK_STATIC`` (default **n**)
-
-- Embed static flavour of the dependencies **libibverbs** and **libmlx4**
-+ Embed static flavor of the dependencies **libibverbs** and **libmlx4**
- in the PMD shared library or the executable static binary.
-
@@ -413 +369 @@
-index 5fa6b6252..af1e408ea 100644
+index bfa6cf162..cee167bfe 100644
@@ -423,7 +378,0 @@
-@@ -217,5 +217,5 @@ These options can be modified in the ``.config`` file.
- - ``CONFIG_RTE_IBVERBS_LINK_STATIC`` (default **n**)
-
-- Embed static flavour of the dependencies **libibverbs** and **libmlx5**
-+ Embed static flavor of the dependencies **libibverbs** and **libmlx5**
- in the PMD shared library or the executable static binary.
-
@@ -431 +380 @@
-index 09e2f2a56..bacc013d4 100644
+index b2ddeab50..f63d85875 100644
@@ -452,24 +400,0 @@
-diff --git a/doc/guides/nics/nfb.rst b/doc/guides/nics/nfb.rst
-index a7fb963ca..8df76c077 100644
---- a/doc/guides/nics/nfb.rst
-+++ b/doc/guides/nics/nfb.rst
-@@ -82,5 +82,5 @@ Ethernet port may be sent to any queue.
- They are represented in DPDK as a single port.
-
--NFB-200G2QL card employs an addon cable which allows to connect it to two
-+NFB-200G2QL card employs an add-on cable which allows to connect it to two
- physical PCI-E slots at the same time (see the diagram below).
- This is done to allow 200 Gbps of traffic to be transferred through the PCI-E
-diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst
-index 09a8529b9..309fa5d39 100644
---- a/doc/guides/nics/nfp.rst
-+++ b/doc/guides/nics/nfp.rst
-@@ -150,6 +150,6 @@ PF multiprocess support
-
- Due to how the driver needs to access the NFP through a CPP interface, which implies
--to use specific registers inside the chip, the number of secondary proceses with PF
--ports is limitted to only one.
-+to use specific registers inside the chip, the number of secondary processes with PF
-+ports is limited to only one.
-
- This limitation will be solved in future versions but having basic multiprocess support
@@ -477 +402 @@
-index eb47f25e3..6d01d05b0 100644
+index 40065284b..f449b19d6 100644
@@ -487,2 +412,2 @@
-@@ -210,10 +210,10 @@ Validating flow rules depends on the firmware variant.
- The :ref:`flow_isolated_mode` is supported.
+@@ -208,10 +208,10 @@ Supported actions:
+ Validating flow rules depends on the firmware variant.
@@ -502 +427 @@
-@@ -349,8 +349,8 @@ boolean parameters value.
+@@ -347,8 +347,8 @@ boolean parameters value.
@@ -525 +450 @@
-index 063bd0be4..4b6d77d37 100644
+index 9a3d7b348..14c669b7b 100644
@@ -554 +479 @@
-index 82aae0ab2..c21bb193f 100644
+index 5a64406eb..2586af0ff 100644
@@ -590 +515 @@
-index ad9703753..a06c835a0 100644
+index 87e264906..3ba4238ce 100644
@@ -615 +540 @@
-index 74a930b6d..23fa5bc18 100644
+index 8ee33c875..23770ffd4 100644
@@ -632 +557 @@
-@@ -397,5 +397,5 @@ Operation Management and Allocation
+@@ -383,5 +383,5 @@ Operation Management and Allocation
@@ -639 +564 @@
-@@ -603,5 +603,5 @@ Sample code
+@@ -587,5 +587,5 @@ Sample code
@@ -646 +571 @@
-@@ -808,5 +808,5 @@ using one of the crypto PMDs available in DPDK.
+@@ -768,5 +768,5 @@ using one of the crypto PMDs available in DPDK.
@@ -653 +578 @@
-@@ -887,5 +887,5 @@ Not all asymmetric crypto xforms are supported for chaining. Currently supported
+@@ -847,5 +847,5 @@ Not all asymmetric crypto xforms are supported for chaining. Currently supported
@@ -661 +586 @@
-index 96dbf30e0..74dba4dd1 100644
+index 002d973a4..a851a8112 100644
@@ -664 +589 @@
-@@ -205,5 +205,5 @@ Which ``dpdk-pmdinfogen`` scans for. Using this information other relevant
+@@ -248,5 +248,5 @@ Which ``dpdk-pmdinfogen`` scans for. Using this information other relevant
@@ -683 +608 @@
-index fa8afdb3a..c27f730c7 100644
+index 888ce7801..94d19682e 100644
@@ -686 +611 @@
-@@ -734,5 +734,5 @@ The most important fields in the structure and how they are used are described b
+@@ -649,5 +649,5 @@ The most important fields in the structure and how they are used are described b
@@ -694 +619 @@
-index e95529974..c7dda9221 100644
+index 0166bb45d..7bc559c8a 100644
@@ -697 +622 @@
-@@ -163,5 +163,5 @@ is applicable when the adapter uses a service core function. The application
+@@ -158,5 +158,5 @@ is applicable when the adapter uses a service core function. The application
@@ -704 +629 @@
-@@ -181,7 +181,7 @@ For SW based packet transfers, i.e., when the
+@@ -176,7 +176,7 @@ For SW based packet transfers, i.e., when the
@@ -715 +640 @@
-index dcdfeb75e..7bcd7603b 100644
+index 8fcae5469..27c51d256 100644
@@ -739,53 +663,0 @@
-diff --git a/doc/guides/prog_guide/ipsec_lib.rst b/doc/guides/prog_guide/ipsec_lib.rst
-index 84696d4cf..6fc08886f 100644
---- a/doc/guides/prog_guide/ipsec_lib.rst
-+++ b/doc/guides/prog_guide/ipsec_lib.rst
-@@ -66,5 +66,5 @@ In that mode the library functions perform
- - check SQN
- - prepare *rte_crypto_op* structure for each input packet
-- - verify that integity check and decryption performed by crypto device
-+ - verify that integrity check and decryption performed by crypto device
- completed successfully
- - check padding data
-@@ -89,5 +89,5 @@ In that mode the library functions perform
- * for inbound packets:
-
-- - verify that integity check and decryption performed by *rte_security*
-+ - verify that integrity check and decryption performed by *rte_security*
- device completed successfully
- - check SQN
-@@ -102,8 +102,8 @@ In that mode the library functions perform
- - add outer IP header (tunnel mode) / update IP header (transport mode)
- - add ESP header and trailer, padding and IV data
-- - update *ol_flags* inside *struct rte_mbuf* to inidicate that
-+ - update *ol_flags* inside *struct rte_mbuf* to indicate that
- inline-crypto processing has to be performed by HW on this packet
- - invoke *rte_security* device specific *set_pkt_metadata()* to associate
-- secuirty device specific data with the packet
-+ security device specific data with the packet
-
- RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL
-@@ -114,13 +114,13 @@ In that mode the library functions perform
- * for inbound packets:
-
-- - verify that integity check and decryption performed by *rte_security*
-+ - verify that integrity check and decryption performed by *rte_security*
- device completed successfully
-
- * for outbound packets:
-
-- - update *ol_flags* inside *struct rte_mbuf* to inidicate that
-+ - update *ol_flags* inside *struct rte_mbuf* to indicate that
- inline-crypto processing has to be performed by HW on this packet
- - invoke *rte_security* device specific *set_pkt_metadata()* to associate
-- secuirty device specific data with the packet
-+ security device specific data with the packet
-
- RTE_SECURITY_ACTION_TYPE_LOOKASIDE_PROTOCOL
-@@ -132,5 +132,5 @@ In that mode the library functions perform
-
- - prepare *rte_crypto_op* structure for each input packet
-- - verify that integity check and decryption performed by crypto device
-+ - verify that integrity check and decryption performed by crypto device
- completed successfully
-
@@ -793 +665 @@
-index 7fcbd936f..daf87f4a8 100644
+index 33ea980e5..7b8a481a6 100644
@@ -796 +668 @@
-@@ -228,5 +228,5 @@ application functions:
+@@ -226,5 +226,5 @@ application functions:
@@ -826 +698 @@
-index 5af795c0d..a36ebef4d 100644
+index 02f05614a..c1b29f937 100644
@@ -844 +716 @@
-index 0203f4f61..937f52bce 100644
+index dbf4999aa..4e9b4440b 100644
@@ -847 +719 @@
-@@ -2130,5 +2130,5 @@ as defined in the ``rte_flow_action_raw_decap``
+@@ -2132,5 +2132,5 @@ as defined in the ``rte_flow_action_raw_decap``
@@ -854 +726 @@
-@@ -2280,5 +2280,5 @@ Decrease TTL value.
+@@ -2282,5 +2282,5 @@ Decrease TTL value.
@@ -861 +733 @@
-@@ -2298,5 +2298,5 @@ Assigns a new TTL value.
+@@ -2300,5 +2300,5 @@ Assigns a new TTL value.
@@ -961 +833 @@
-index a86c07a62..fc3ee4353 100644
+index c77df338f..27c3af8f9 100644
@@ -1048 +920 @@
-index 40a3264ab..405e706a4 100644
+index 653f972f3..6ade9c6e1 100644
@@ -1106 +978 @@
-index 3d784e705..ac118c1a2 100644
+index 4869a011d..5f7d39736 100644
@@ -1118,14 +989,0 @@
-@@ -125,5 +125,5 @@ Where:
- (available only with librte_ipsec code path).
-
--* ``-a``: enables Security Association sequence number atomic behaviour
-+* ``-a``: enables Security Association sequence number atomic behavior
- (available only with librte_ipsec code path).
-
-@@ -753,5 +753,5 @@ DUT OS(NIC1)--(IPsec)-->(NIC1)ipsec-secgw(TAP)--(plain)-->(TAP)SUT OS
- SUT OS(TAP)--(plain)-->(TAP)psec-secgw(NIC1)--(IPsec)-->(NIC1)DUT OS
-
--It then tries to perform some data transfer using the scheme decribed above.
-+It then tries to perform some data transfer using the scheme described above.
-
- usage
@@ -1133 +991 @@
-index e2c04efcc..ac6ee8ac2 100644
+index fbd30a5ea..96f0fc6fd 100644
@@ -1156 +1014 @@
-index 5f313c529..5aefd8d89 100644
+index a9370c80b..af9665b2c 100644
@@ -1162,2 +1020,2 @@
--The application is located in the ``$RTE_SDK/app/test-pipline`` directory.
-+The application is located in the ``$RTE_SDK/app/test-pipeline`` directory.
+-The application is located in the ``$RTE_SDK/test/test-pipline`` directory.
++The application is located in the ``$RTE_SDK/test/test-pipeline`` directory.
@@ -1196 +1054 @@
-index 14d432e78..109d10957 100644
+index 5be9f24d5..57758ca00 100644
@@ -1199 +1057 @@
-@@ -345,5 +345,5 @@ monitoring of branch ratio on cores doing busy polling via PMDs.
+@@ -340,5 +340,5 @@ monitoring of branch ratio on cores doing busy polling via PMDs.
@@ -1206 +1064 @@
-@@ -385,5 +385,5 @@ the file.
+@@ -380,5 +380,5 @@ the file.
@@ -1213 +1071 @@
-@@ -735,5 +735,5 @@ policy down to the host application. These parameters are as follows:
+@@ -730,5 +730,5 @@ policy down to the host application. These parameters are as follows:
@@ -1220 +1078 @@
-@@ -743,5 +743,5 @@ policy down to the host application. These parameters are as follows:
+@@ -738,5 +738,5 @@ policy down to the host application. These parameters are as follows:
@@ -1227 +1085 @@
-@@ -751,5 +751,5 @@ policy down to the host application. These parameters are as follows:
+@@ -746,5 +746,5 @@ policy down to the host application. These parameters are as follows:
@@ -1235 +1093 @@
-index fdf6ec7f9..e7db52068 100644
+index e934b4bed..89df03166 100644
@@ -1238 +1096 @@
-@@ -382,5 +382,5 @@ The command line options are:
+@@ -366,5 +366,5 @@ The command line options are:
@@ -1245 +1103 @@
-@@ -422,5 +422,5 @@ The command line options are:
+@@ -406,5 +406,5 @@ The command line options are:
@@ -1252 +1110 @@
-@@ -428,15 +428,15 @@ The command line options are:
+@@ -412,14 +412,14 @@ The command line options are:
@@ -1270 +1127,0 @@
-
@@ -1272 +1129 @@
-index 5d4dc6f0c..e602df560 100644
+index d4e3fd8a5..34f7bc766 100644
@@ -1275 +1132 @@
-@@ -304,5 +304,5 @@ The available information categories are:
+@@ -303,5 +303,5 @@ The available information categories are:
@@ -1282 +1139 @@
-@@ -327,5 +327,5 @@ The available information categories are:
+@@ -326,5 +326,5 @@ The available information categories are:
@@ -1289 +1146 @@
-@@ -2290,5 +2290,5 @@ set bonding lacp dedicated_queue
+@@ -2247,5 +2247,5 @@ set bonding lacp dedicated_queue
@@ -1296 +1153 @@
-@@ -2298,5 +2298,5 @@ set bonding agg_mode
+@@ -2255,5 +2255,5 @@ set bonding agg_mode
@@ -1303 +1160 @@
-@@ -2692,6 +2692,6 @@ where:
+@@ -2649,6 +2649,6 @@ where:
@@ -1312 +1169 @@
-@@ -2744,5 +2744,5 @@ Add port traffic management hierarchy nonleaf node
+@@ -2701,5 +2701,5 @@ Add port traffic management hierarchy nonleaf node
@@ -1319 +1176 @@
-@@ -2759,5 +2759,5 @@ where:
+@@ -2716,5 +2716,5 @@ where:
@@ -1326 +1183 @@
-@@ -2770,5 +2770,5 @@ Add port traffic management hierarchy leaf node
+@@ -2727,5 +2727,5 @@ Add port traffic management hierarchy leaf node
@@ -1333 +1190 @@
-@@ -2785,5 +2785,5 @@ where:
+@@ -2742,5 +2742,5 @@ where:
@@ -1340 +1197 @@
-@@ -2797,5 +2797,5 @@ Delete port traffic management hierarchy node
+@@ -2754,5 +2754,5 @@ Delete port traffic management hierarchy node
@@ -1347 +1204 @@
-@@ -3990,5 +3990,5 @@ This section lists supported actions and their attributes, if any.
+@@ -3947,5 +3947,5 @@ This section lists supported actions and their attributes, if any.
@@ -1354 +1211 @@
-@@ -4523,5 +4523,5 @@ bpf-load
+@@ -4468,5 +4468,5 @@ bpf-load
@@ -1361 +1218 @@
-@@ -4561,5 +4561,5 @@ bpf-unload
+@@ -4506,5 +4506,5 @@ bpf-unload
@@ -1432 +1289 @@
-index 6bdf5a861..2ea1b59c2 100644
+index d5b5ed6a6..e9a0b79d3 100644
@@ -1435,15 +1292 @@
-@@ -45,5 +45,5 @@ If no port mask is specified xstats are reset for all DPDK ports.
-
- **--show-port**
--The show-port parameter displays port level various configuration informationi
-+The show-port parameter displays port level various configuration information
- associated to RX port queue pair.
-
-@@ -57,5 +57,5 @@ settings and stats per node.
-
- **--show-ring[=name]**
--The show-ring pararmeter display current allocation of all ring with
-+The show-ring parameter display current allocation of all ring with
- debug information. Specifying the name allows to display details for specific
- ring. For invalid or no ring name, whole list is dump.
-@@ -77,5 +77,5 @@ Limitations
+@@ -49,5 +49,5 @@ Limitations
@@ -1457 +1300 @@
-index 07da35e52..7e6a4db2e 100644
+index af38b1632..a8cb6fbbe 100644
next prev parent reply other threads:[~2019-05-08 16:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 16:01 [dpdk-stable] patch 'raw/dpaa2_qdma: fix spin lock release' " Kevin Traynor
2019-05-08 16:01 ` [dpdk-stable] patch 'raw/ifpga: fix file descriptor leak in error path' " Kevin Traynor
2019-05-08 16:02 ` Kevin Traynor [this message]
2019-05-08 16:02 ` [dpdk-stable] patch 'doc: fix spelling reported by aspell in comments' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'examples/multi_process: fix buffer underrun' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'examples/power: fix buffer overrun' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'examples/power: fix json null termination' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'eal: fix formatting of hotplug error message' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'ipc: fix memory leak on request failure' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/tap: fix memory leak on IPC request' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'ipc: fix send error handling' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'ipc: harden message receive' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'ipc: handle more invalid parameter cases' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'event/dsw: fix capability flags' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/mlx5: fix comments mixing Rx and Tx' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'doc: fix interactive commands in testpmd guide' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'app/testpmd: fix help info for interactive commands' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/ring: fix coding style' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/ring: avoid hard-coded length' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/ring: use calloc style where appropriate' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/ring: check length of ring name' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/ring: fix return value check' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/kni: " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'app/testpmd: fix unintentional integer overflow' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/i40e: fix queue number check' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'test/bonding: fix MAC assignment for re-run' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/i40e: fix link speed for X722' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/mlx5: check Tx queue size overflow' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/mlx5: fix max number of queues for NEON Tx' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/tap: fix potential IPC buffer overrun' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/vmxnet3: add VLAN filter capability' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'net/netvsc: reset mbuf port on VF Rx' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'test: clean remaining trace of devargs autotest' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'eventdev: update references to removed function' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'hash: fix doc about thread/process safety' " Kevin Traynor
2019-05-08 16:02 ` [dpdk-stable] patch 'doc: fix broken link in LPM guide' " Kevin Traynor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190508160233.2648-3-ktraynor@redhat.com \
--to=ktraynor@redhat.com \
--cc=john.mcnamara@intel.com \
--cc=ramirose@gmail.com \
--cc=stable@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).