1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright(c) 2017 Intel Corporation
4 dpdk-test-bbdev Application
5 ===========================
7 The ``dpdk-test-bbdev`` tool is a Data Plane Development Kit (DPDK) utility that
8 allows measuring performance parameters of PMDs available in the bbdev framework.
9 Available tests available for execution are: latency, throughput, validation and
10 sanity tests. Execution of tests can be customized using various parameters
11 passed to a python running script.
13 Compiling the Application
14 -------------------------
16 **Step 1: PMD setting**
18 The ``dpdk-test-bbdev`` tool depends on crypto device drivers PMD which
19 are disabled by default in the build configuration file ``common_base``.
20 The bbdevice drivers PMD which should be tested can be enabled by setting
22 ``CONFIG_RTE_LIBRTE_PMD_<name>=y``
24 Setting example for (*turbo_sw*) PMD
26 ``CONFIG_RTE_LIBRTE_PMD_BBDEV_TURBO_SW=y``
28 **Step 2: Build the application**
30 Execute the ``dpdk-setup.sh`` script to build the DPDK library together with the
31 ``dpdk-test-bbdev`` application.
33 Initially, the user must select a DPDK target to choose the correct target type
34 and compiler options to use when building the libraries.
35 The user must have all libraries, modules, updates and compilers installed
36 in the system prior to this, as described in the earlier chapters in this
37 Getting Started Guide.
39 Running the Application
40 -----------------------
42 The tool application has a number of command line options:
44 .. code-block:: console
46 python test-bbdev.py [-h] [-p TESTAPP_PATH] [-e EAL_PARAMS] [-t TIMEOUT]
47 [-c TEST_CASE [TEST_CASE ...]]
48 [-v TEST_VECTOR [TEST_VECTOR...]] [-n NUM_OPS]
49 [-b BURST_SIZE [BURST_SIZE ...]] [-l NUM_LCORES]
54 The following are the command-line options:
57 Shows help message and exit.
59 ``-p TESTAPP_PATH, --testapp_path TESTAPP_PATH``
60 Indicates the path to the bbdev test app. If not specified path is set based
61 on *$RTE_SDK* environment variable concatenated with "*/build/app/testbbdev*".
63 ``-e EAL_PARAMS, --eal_params EAL_PARAMS``
64 Specifies EAL arguments which are passed to the test app. For more details,
65 refer to DPDK documentation at http://dpdk.org/doc.
67 ``-t TIMEOUT, --timeout TIMEOUT``
68 Specifies timeout in seconds. If not specified timeout is set to 300 seconds.
70 ``-c TEST_CASE [TEST_CASE ...], --test_cases TEST_CASE [TEST_CASE ...]``
71 Defines test cases to run. If not specified all available tests are run.
73 The following tests can be run:
76 Small unit tests witch check basic functionality of bbdev library.
78 Test calculates three latency metrics:
81 measures the cost of offloading enqueue and dequeue operations.
82 * offload_latency_empty_q_tc
83 measures the cost of offloading a dequeue operation from an empty queue.
84 checks how long last dequeueing if there is no operations to dequeue
85 * operation_latency_tc
86 measures the time difference from the first attempt to enqueue till the
87 first successful dequeue.
89 Test do enqueue on given vector and compare output after dequeueing.
91 Test measures the achieved throughput on the available lcores.
92 Results are printed in million operations per second and million bits per second.
94 The same test as 'throughput' but uses interrupts instead of PMD to perform
99 ``./test-bbdev.py -c validation``
100 Runs validation test suite
102 ``./test-bbdev.py -c latency throughput``
103 Runs latency and throughput test suites
105 ``-v TEST_VECTOR [TEST_VECTOR ...], --test_vector TEST_VECTOR [TEST_VECTOR ...]``
106 Specifies paths to the test vector files. If not specified path is set based
107 on *$RTE_SDK* environment variable concatenated with
108 "*/app/test-bbdev/test_vectors/bbdev_vector_null.data*" and indicates default
113 ``./test-bbdev.py -v app/test-bbdev/test_vectors/bbdev_vector_td_test1.data``
114 Fills vector based on bbdev_vector_td_test1.data file and runs all tests
116 ``./test-bbdev.py -v bbdev_vector_td_test1.data bbdev_vector_te_test2.data``
117 The bbdev test app is executed twice. First time vector is filled based on
118 *bbdev_vector_td_test1.data* file and second time based on
119 *bbdev_vector_te_test2.data* file. For both executions all tests are run.
121 ``-n NUM_OPS, --num_ops NUM_OPS``
122 Specifies number of operations to process on device. If not specified num_ops
123 is set to 32 operations.
125 ``-l NUM_LCORES, --num_lcores NUM_LCORES``
126 Specifies number of lcores to run. If not specified num_lcores is set
127 according to value from RTE configuration (EAL coremask)
129 ``-b BURST_SIZE [BURST_SIZE ...], --burst-size BURST_SIZE [BURST_SIZE ...]``
130 Specifies operations enqueue/dequeue burst size. If not specified burst_size is
131 set to 32. Maximum is 512.
137 Thanks to the globbing functionality in python test-bbdev.py script allows to
138 run tests with different set of vector files without giving all of them explicitly.
142 .. code-block:: console
144 ./test-bbdev.py -v app/test-bbdev/test_vectors/bbdev_vector_*.data
146 It runs all tests with following vectors:
148 - ``bbdev_vector_null.data``
150 - ``bbdev_vector_td_default.data``
152 - ``bbdev_vector_te_default.data``
154 - ``turbo_enc_c1_k40_r0_e1190_rm.data``
156 - ``turbo_enc_c1_k40_r0_e1194_rm.data``
158 - ``turbo_enc_c1_k40_r0_e1196_rm.data``
160 - ``turbo_enc_c1_k40_r0_e272_rm.data``
162 .. code-block:: console
164 ./test-bbdev.py -v app/test-bbdev/test_vectors/bbdev_vector_t?_default.data
166 It runs all tests with "default" vectors:
168 - ``bbdev_vector_te_default.data``
170 - ``bbdev_vector_td_default.data``
176 Shortened tree of isg_cid-wireless_dpdk_ae with dpdk compiled for
177 x86_64-native-linuxapp-icc target:
184 |-- bbdev_vector_null.data
185 |-- bbdev_vector_td_default.data
186 |-- bbdev_vector_te_default.data
188 |-- x86_64-native-linuxapp-icc
195 .. code-block:: console
197 ./test-bbdev.py -p ../../x86_64-native-linuxapp-icc/app/testbbdev
198 -v ./test_vectors/bbdev_vector_td_default.data
200 It runs all available tests using the test vector filled based on
201 *bbdev_vector_td_default.data* file.
202 By default number of operations to process on device is set to 32, timeout is
203 set to 300s and operations enqueue/dequeue burst size is set to 32.
204 Moreover a bbdev (*bbdev_null*) device will be created.
206 bbdev turbo_sw device
207 ~~~~~~~~~~~~~~~~~~~~~
209 .. code-block:: console
211 ./test-bbdev.py -p ../../x86_64-native-linuxapp-icc/app/testbbdev
212 -e="--vdev=turbo_sw" -t 120 -c validation
213 -v ./test_vectors/bbdev_vector_t?_default.data -n 64 -b 8 32
215 It runs **validation** test for each vector file that matches the given pattern.
216 Number of operations to process on device is set to 64 and operations timeout is
217 set to 120s and enqueue/dequeue burst size is set to 8 and to 32.
218 Moreover a bbdev (*turbo_sw*) device will be created.
224 Executing bbdev null device with *bbdev_vector_null.data* helps in measuring the
225 overhead introduced by the bbdev framework.
227 .. code-block:: console
229 ./test-bbdev.py -e="--vdev=bbdev_null0"
230 -v ./test_vectors/bbdev_vector_null.data
234 bbdev_null device does not have to be defined explicitly as it is created by default.
241 Test Vector files contain the data which is used to set turbo decoder/encoder
242 parameters and buffers for validation purpose. New test vector files should be
243 stored in ``app/test-bbdev/test_vectors/`` directory. Detailed description of
244 the syntax of the test vector files is in the following section.
247 Basic principles for test vector files
248 --------------------------------------
249 Line started with ``#`` is treated as a comment and is ignored.
251 If variable is a chain of values, values should be separated by a comma. If
252 assignment is split into several lines, each line (except the last one) has to
253 be ended with a comma.
254 There is no comma after last value in last line. Correct assignment should
255 look like the following:
260 value, value, value, value,
263 In case where variable is a single value correct assignment looks like the
271 Length of chain variable is calculated by parser. Can not be defined
274 Variable op_type has to be defined as a first variable in file. It specifies
275 what type of operations will be executed. For decoder op_type has to be set to
276 ``RTE_BBDEV_OP_TURBO_DEC`` and for encoder to ``RTE_BBDEV_OP_TURBO_ENC``.
278 Full details of the meaning and valid values for the below fields are
279 documented in *rte_bbdev_op.h*
282 Turbo decoder test vectors template
283 -----------------------------------
285 For turbo decoder it has to be always set to ``RTE_BBDEV_OP_TURBO_DEC``
290 RTE_BBDEV_OP_TURBO_DEC
292 Chain of uint32_t values. Note that it is possible to define more than one
293 input/output entries which will result in chaining two or more data structures
294 for *segmented Transport Blocks*
299 0x00000000, 0x7f817f00, 0x7f7f8100, 0x817f8100, 0x81008100, 0x7f818100, 0x81817f00, 0x7f818100,
300 0x81007f00, 0x7f818100, 0x817f8100, 0x81817f00, 0x81008100, 0x817f7f00, 0x7f7f8100, 0x81817f00
302 Chain of uint32_t values
307 0x7f7f0000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000,
308 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
310 Chain of uint32_t values
315 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000,
316 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
318 Chain of uint32_t values
325 Chain of uint32_t values
332 Chain of uint32_t values
337 0x817f817f, 0x7f817f7f, 0x81818181, 0x817f7f81, 0x7f818181, 0x8181817f, 0x817f817f, 0x8181817f
339 Chain of uint32_t values
344 0x817f7f81, 0x7f7f7f81, 0x7f7f8181
385 expected_iter_count =
402 Chain of flags for turbo decoder operation. Following flags can be used:
404 - ``RTE_BBDEV_TURBO_SUBBLOCK_DEINTERLEAVE``
406 - ``RTE_BBDEV_TURBO_CRC_TYPE_24B``
408 - ``RTE_BBDEV_TURBO_EQUALIZER``
410 - ``RTE_BBDEV_TURBO_SOFT_OUT_SATURATE``
412 - ``RTE_BBDEV_TURBO_HALF_ITERATION_EVEN``
414 - ``RTE_BBDEV_TURBO_CONTINUE_CRC_MATCH``
416 - ``RTE_BBDEV_TURBO_SOFT_OUTPUT``
418 - ``RTE_BBDEV_TURBO_EARLY_TERMINATION``
420 - ``RTE_BBDEV_TURBO_DEC_INTERRUPTS``
422 - ``RTE_BBDEV_TURBO_POS_LLR_1_BIT_IN``
424 - ``RTE_BBDEV_TURBO_NEG_LLR_1_BIT_IN``
426 - ``RTE_BBDEV_TURBO_POS_LLR_1_BIT_SOFT_OUT``
428 - ``RTE_BBDEV_TURBO_NEG_LLR_1_BIT_SOFT_OUT``
430 - ``RTE_BBDEV_TURBO_MAP_DEC``
437 RTE_BBDEV_TURBO_SUBBLOCK_DEINTERLEAVE, RTE_BBDEV_TURBO_EQUALIZER,
438 RTE_BBDEV_TURBO_SOFT_OUTPUT
440 Chain of operation statuses that are expected after operation is performed.
441 Following statuses can be used:
451 ``OK`` means no errors are expected. Cannot be used with other values.
459 Turbo encoder test vectors template
460 -----------------------------------
462 For turbo encoder it has to be always set to ``RTE_BBDEV_OP_TURBO_ENC``
467 RTE_BBDEV_OP_TURBO_ENC
469 Chain of uint32_t values
476 Chain of uint32_t values
481 0xd2399179, 0x640eb999, 0x2cbaf577, 0xaf224ae2, 0x9d139927, 0xe6909b29,
482 0xa25b7f47, 0x2aa224ce, 0x79f2
512 Chain of flags for turbo encoder operation. Following flags can be used:
514 - ``RTE_BBDEV_TURBO_RV_INDEX_BYPASS``
516 - ``RTE_BBDEV_TURBO_RATE_MATCH``
518 - ``RTE_BBDEV_TURBO_CRC_24B_ATTACH``
520 - ``RTE_BBDEV_TURBO_CRC_24A_ATTACH``
522 - ``RTE_BBDEV_TURBO_ENC_SCATTER_GATHER``
524 ``RTE_BBDEV_TURBO_ENC_SCATTER_GATHER`` is used to indicate the parser to
525 force the input data to be memory split and formed as a segmented mbuf.
531 RTE_BBDEV_TURBO_RATE_MATCH
533 Chain of operation statuses that are expected after operation is performed.
534 Following statuses can be used:
542 ``OK`` means no errors are expected. Cannot be used with other values.