The word sanity check is unnecessary here.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
doc/guides/gpus/cuda.rst | 2 +-
doc/guides/sample_app_ug/eventdev_pipeline.rst | 2 +-
doc/guides/tools/testbbdev.rst | 8 ++++----
3 files changed, 6 insertions(+), 6 deletions(-)
@@ -81,7 +81,7 @@ Similarly to CUDA shared library, if the **libgdrapi.so** shared library
is not installed in default locations (e.g. /usr/local/lib),
you can use the variable ``GDRCOPY_PATH_L``.
-As an example, to enable the CPU map feature sanity check,
+As an example, to enable the CPU map feature check,
run the ``app/test-gpudev`` application with:
.. code-block:: console
@@ -50,7 +50,7 @@ these settings is shown below:
./<build_dir>/examples/dpdk-eventdev_pipeline -l 0,2,8-15 --vdev event_sw0 \
-- -r1 -t1 -e4 -w FF00 -s4 -n0 -c32 -W1000 -D
-The application has some sanity checking built-in, so if there is a function
+The application has some internal validation, so if there is a function
(e.g.; the RX core) which doesn't have a cpu core mask assigned, the application
will print an error message:
@@ -7,7 +7,7 @@ dpdk-test-bbdev Application
The ``dpdk-test-bbdev`` tool is a Data Plane Development Kit (DPDK) utility that
allows measuring performance parameters of PMDs available in the bbdev framework.
Tests available for execution are: latency, throughput, validation,
-bler and sanity tests. Execution of tests can be customized using various
+bler and basic functionality. Execution of tests can be customized using various
parameters passed to a python running script.
@@ -95,8 +95,8 @@ Test Cases
There are 7 main test cases that can be executed using testbbdev tool:
-* Sanity checks [-c unittest]
- - Performs sanity checks on BBDEV interface, validating basic functionality
+* Functional checks [-c unittest]
+ - Performs checks on BBDEV interface, validating basic functionality
* Validation tests [-c validation]
- Performs full operation of enqueue and dequeue
@@ -230,7 +230,7 @@ vector name refer more explicitly processing specificity such as
is purely read/written for external DDR, lbrm when limited buffer
rate matching is expected, or crc_fail when a CRC failure is expected.
They are chosen to have a good coverage across sizes and processing
-parameters while still keeping their number limited as part of sanity
+parameters while still keeping their number limited as part of functional
regression.
Shortened tree of isg_cid-wireless_dpdk_ae with dpdk compiled and output