blob: 23b98c8f4dcd3881a3a0fc77a4b59ffa2ad76e51 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
.. This work is licensed under a Creative Commons Attribution 4.0 International
.. License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) OPNFV, ZTE and others.
***************************************
Yardstick Test Case Description TC042
***************************************
.. _DPDK: http://dpdk.org/doc/guides/index.html
.. _Testpmd: http://dpdk.org/doc/guides/testpmd_app_ug/index.html
.. _Pktgen-dpdk: https://pktgen-dpdk.readthedocs.io/en/latest/index.html
+-----------------------------------------------------------------------------+
|Network Performance |
| |
+--------------+--------------------------------------------------------------+
|test case id | OPNFV_YARDSTICK_TC042_DPDK pktgen latency measurements |
| | |
+--------------+--------------------------------------------------------------+
|metric | L2 Network Latency |
| | |
+--------------+--------------------------------------------------------------+
|test purpose | Measure L2 network latency when DPDK is enabled between hosts|
| | on different compute blades. |
| | |
+--------------+--------------------------------------------------------------+
|configuration | file: opnfv_yardstick_tc042.yaml |
| | |
| | * Packet size: 64 bytes |
| | * SLA(max_latency): 100usec |
| | |
+--------------+--------------------------------------------------------------+
|test tool | DPDK_ |
| | Pktgen-dpdk_ |
| | |
| | (DPDK and Pktgen-dpdk are not part of a Linux distribution, |
| | hence they needs to be installed. |
| | As an example see the /yardstick/tools/ directory for how to |
| | generate a Linux image with DPDK and pktgen-dpdk included.) |
| | |
+--------------+--------------------------------------------------------------+
|references | DPDK_ |
| | |
| | Pktgen-dpdk_ |
| | |
| | ETSI-NFV-TST001 |
| | |
+--------------+--------------------------------------------------------------+
|applicability | Test can be configured with different packet sizes. Default |
| | values exist. |
| | |
+--------------+--------------------------------------------------------------+
|pre-test | The test case image needs to be installed into Glance |
|conditions | with DPDK and pktgen-dpdk included in it. |
| | |
| | The NICs of compute nodes must support DPDK on POD. |
| | |
| | And at least compute nodes setup hugepage. |
| | |
| | If you want to achievement a hight performance result, it is |
| | recommend to use NUAM, CPU pin, OVS and so on. |
| | |
+--------------+--------------------------------------------------------------+
|test sequence | description and expected result |
| | |
+--------------+--------------------------------------------------------------+
|step 1 | The hosts are installed on different blades, as server and |
| | client. Both server and client have three interfaces. The |
| | first one is management such as ssh. The other two are used |
| | by DPDK. |
| | |
+--------------+--------------------------------------------------------------+
|step 2 | Testpmd_ is invoked with configurations to forward packets |
| | from one DPDK port to the other on server. |
| | |
+--------------+--------------------------------------------------------------+
|step 3 | Pktgen-dpdk is invoked with configurations as a traffic |
| | generator and logs are produced and stored on client. |
| | |
| | Result: Logs are stored. |
| | |
+--------------+--------------------------------------------------------------+
|test verdict | Fails only if SLA is not passed, or if there is a test case |
| | execution problem. |
| | |
+--------------+--------------------------------------------------------------+
|
