From: Thierry Herbelot <thierry.herbelot@6wind.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>, stable@dpdk.org
Subject: [dpdk-dev] [PATCH] doc/guides/nics: fix typos
Date: Fri, 18 Oct 2019 17:06:57 +0200 [thread overview]
Message-ID: <20191018150657.17600-1-thierry.herbelot@6wind.com> (raw)
'CRC striping' should be spelled 'CRC stripping'.
Fixes: 3eee1f067e7c ('fm10k: add guide')
Fixes: 7a4d9f6676d7 ('doc: add liquidio')
Fixes: f820b5896631 ('doc: add octeontx ethdev driver documentation')
Fixes: 920717e4d8ba ('net/octeontx2: add device start operation')
Fixes: f994cecafdcf ('doc: add ThunderX nicvf')
Cc: stable@dpdk.org
Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>
---
doc/guides/nics/fm10k.rst | 4 ++--
doc/guides/nics/liquidio.rst | 4 ++--
doc/guides/nics/octeontx.rst | 4 ++--
doc/guides/nics/octeontx2.rst | 4 ++--
doc/guides/nics/thunderx.rst | 4 ++--
5 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/doc/guides/nics/fm10k.rst b/doc/guides/nics/fm10k.rst
index 764e089c8616..20a1cde53590 100644
--- a/doc/guides/nics/fm10k.rst
+++ b/doc/guides/nics/fm10k.rst
@@ -135,8 +135,8 @@ the Rx/Tx queues. When switch comes up, a LSC event indicating ``LINK_UP`` is
sent to the app, which can then restart the FM10000 port to resume network
processing.
-CRC striping
-~~~~~~~~~~~~
+CRC stripping
+~~~~~~~~~~~~~
The FM10000 family of NICs strip the CRC for every packets coming into the
host interface. So, keeping CRC is not supported.
diff --git a/doc/guides/nics/liquidio.rst b/doc/guides/nics/liquidio.rst
index e2a38004d0d6..0534146720f1 100644
--- a/doc/guides/nics/liquidio.rst
+++ b/doc/guides/nics/liquidio.rst
@@ -190,7 +190,7 @@ Ring size
Number of descriptors for Rx/Tx ring should be in the range 128 to 512.
-CRC striping
-~~~~~~~~~~~~
+CRC stripping
+~~~~~~~~~~~~~
LiquidIO adapters strip ethernet FCS of every packet coming to the host interface.
diff --git a/doc/guides/nics/octeontx.rst b/doc/guides/nics/octeontx.rst
index 012a3ec21f2a..3c19c912db08 100644
--- a/doc/guides/nics/octeontx.rst
+++ b/doc/guides/nics/octeontx.rst
@@ -161,8 +161,8 @@ This driver will only work with ``octeontx_fpavf`` external mempool handler
as it is the most performance effective way for packet allocation and Tx buffer
recycling on OCTEON TX SoC platform.
-CRC striping
-~~~~~~~~~~~~
+CRC stripping
+~~~~~~~~~~~~~
The OCTEON TX SoC family NICs strip the CRC for every packets coming into the
host interface irrespective of the offload configuration.
diff --git a/doc/guides/nics/octeontx2.rst b/doc/guides/nics/octeontx2.rst
index 9a76567a8128..2693c3553f7a 100644
--- a/doc/guides/nics/octeontx2.rst
+++ b/doc/guides/nics/octeontx2.rst
@@ -187,8 +187,8 @@ The OCTEON TX2 SoC family NIC has inbuilt HW assisted external mempool manager.
as it is performance wise most effective way for packet allocation and Tx buffer
recycling on OCTEON TX2 SoC platform.
-CRC striping
-~~~~~~~~~~~~
+CRC stripping
+~~~~~~~~~~~~~
The OCTEON TX2 SoC family NICs strip the CRC for every packet being received by
the host interface irrespective of the offload configuration.
diff --git a/doc/guides/nics/thunderx.rst b/doc/guides/nics/thunderx.rst
index 53eaec72a796..3b75a9a9afb5 100644
--- a/doc/guides/nics/thunderx.rst
+++ b/doc/guides/nics/thunderx.rst
@@ -331,8 +331,8 @@ Example:
Limitations
-----------
-CRC striping
-~~~~~~~~~~~~
+CRC stripping
+~~~~~~~~~~~~~
The ThunderX SoC family NICs strip the CRC for every packets coming into the
host interface irrespective of the offload configuration.
--
2.20.1
next reply other threads:[~2019-10-18 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 15:06 Thierry Herbelot [this message]
2019-10-18 16:29 ` Ferruh Yigit
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=20191018150657.17600-1-thierry.herbelot@6wind.com \
--to=thierry.herbelot@6wind.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).