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
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
|
.. Copyright (c) <2010-2017>, Intel Corporation
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
- Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
- Neither the name of Intel Corporation nor the names of its
contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE.
================================
Ethernet Link Flow Control Tests
================================
The support of Ethernet link flow control features by Poll Mode Drivers
consists in:
- At the receive side, if packet buffer is not enough, NIC will send out the
pause frame to peer and ask the peer to slow down the Ethernet frame #
transmission.
- At the transmit side, if pause frame is received, NIC will slow down the
Ethernet frame transmission according to the pause frame.
MAC Control Frame Forwarding consists in:
- Control frames (PAUSE Frames) are taken by the NIC and do not pass to the
host.
- When Flow Control and MAC Control Frame Forwarding are enabled the PAUSE
frames will be passed to the host and can be handled by testpmd.
Note: Priority flow control is not included in this test plan.
Note: the high_water, low_water, pause_time, send_xon are configured into the
NIC register. It is not necessary to validate the accuracy of these parameters.
And what change it can cause. The port_id is used to indicate the NIC to be
configured. In certain case, a system can contain multiple NIC. However the NIC
need not be configured multiple times.
Prerequisites
=============
Assuming that ports ``0`` and ``2`` are connected to a traffic generator,
launch the ``testpmd`` with the following arguments::
./build/app/testpmd -cffffff -n 3 -- -i --burst=1 --txpt=32 \
--txht=8 --txwt=0 --txfreet=0 --rxfreet=64 --mbcache=250 --portmask=0x5
The -n command is used to select the number of memory channels.
It should match the number of memory channels on that setup.
If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When
using vfio, use the following commands to to load the vfio driver and bind it
to the device under test::
modprobe vfio
modprobe vfio-pci
usertools/dpdk-devbind.py --bind=vfio-pci device_bus_id
Test Case: test_perf_flowctrl_on_pause_fwd_on
=============================================
::
testpmd> set flowctrl rx on tx on high_water low_water pause_time
send_xon mac_ctrl_frame_fwd on autoneg on port_id
Setup the ``csum`` forwarding mode::
testpmd> set fwd csum
Set csum packet forwarding mode
Start the packet forwarding::
testpmd> start
csum packet forwarding - CRC stripping disabled - packets/burst=32
nb forwarding cores=1 - nb forwarding ports=10
RX queues=1 - RX desc=128 - RX free threshold=64
RX threshold registers: pthresh=8 hthresh=8 wthresh=4
TX queues=1 - TX desc=512 - TX free threshold=0
TX threshold registers: pthresh=32 hthresh=8 wthresh=8
Validate the NIC can generate the pause frame?
Configure the traffic generator to send IPv4/UDP packet at the length of 66Byte
at the line speed (10G). Because the 66Byte packet cannot reach line rate when
running with testpmd, so it is expected that the pause frame will be sent to the
peer (traffic generator). Ideally this mechanism can avoid the packet loss. And
this depends on high_water/low_water and other parameters are configured properly.
It is strongly recommended that the user look into the data sheet before doing
any flow control configuration. By default, the flow control on 10G is disabled.
the flow control for 1G is enabled.
Validate the NIC can deal with the pause frame.
Configure the traffic generator to send out large amount of pause frames, this
will cause the NIC to disable / slow down the packet transmission according to
the pause time. Once the traffic generator stop sending the pause frame, the NIC
will restore the packet transmission to the expected rate.
Test Case: test_perf_flowctrl_on_pause_fwd_off
==============================================
::
testpmd> set flowctrl rx on tx on high_water low_water pause_time
send_xon mac_ctrl_frame_fwd off autoneg on port_id
Validate same behavior as test_perf_flowctrl_on_pause_fwd_on
Test Case: test_perf_flowctrl_rx_on
===================================
::
testpmd> set flowctrl rx on tx on high_water low_water pause_time
send_xon mac_ctrl_frame_fwd off autoneg on port_id
Validate same behavior as test_perf_flowctrl_on_pause_fwd_on
Test Case: test_perf_flowctrl_off_pause_fwd_off
===============================================
This is the default mode for 10G PMD, by default, testpmd is running on this mode.
no need to execute any command::
testpmd> set flowctrl rx off tx off high_water low_water pause_time
send_xon mac_ctrl_frame_fwd off autoneg on port_id
Validate the NIC won't generate the pause frame when the packet buffer is not
enough. Packet loss can be observed.
Validate the NIC will not slow down the packet transmission after receiving the
pause frame.
Test Case: test_perf_flowctrl_off_pause_fwd_on
==============================================
::
testpmd> set flowctrl rx off tx off high_water low_water pause_time
send_xon mac_ctrl_frame_fwd on autoneg on port_id
Validate same behavior as test_perf_flowctrl_off_pause_fwd_off
Test Case: test_perf_flowctrl_tx_on
===================================
::
testpmd> set flowctrl rx off tx on high_water low_water pause_time
send_xon mac_ctrl_frame_fwd off autoneg on port_id
Validate same behavior as test_perf_flowctrl_on_pause_fwd_off
|
