89. L3 Forwarding Tests

The Layer-3 Forwarding results are produced using l3fwd application.

89.1. Prerequisites

  1. Hardware requirements:

    • For each CPU socket, each memory channel should be populated with at least 1x DIMM

    • Board is populated with 4x 1GbE or 10GbE ports. Special PCIe restrictions may be required for performance. For example, the following requirements should be met for 82599 NICs:

      • NICs are plugged into PCIe Gen2 or Gen3 slots
      • For PCIe Gen2 slots, the number of lanes should be 8x or higher
      • A single port from each NIC should be used, so for 4x ports, 4x NICs should be used

    • NIC ports connected to traffic generator. It is assumed that the NIC ports P0, P1, P2, P3 (as identified by the DPDK application) are connected to the traffic generator ports TG0, TG1, TG2, TG3. The application-side port mask of NIC ports P0, P1, P2, P3 is noted as PORTMASK in this section.

  2. BIOS requirements:

    • Intel Hyper-Threading Technology is ENABLED
    • Hardware Prefetcher is DISABLED
    • Adjacent Cache Line Prefetch is DISABLED
    • Direct Cache Access is DISABLED

  3. Linux kernel requirements:

    • Linux kernel has the following features enabled: huge page support, UIO, HPET
    • Appropriate number of huge pages are reserved at kernel boot time
    • The IDs of the hardware threads (logical cores) per each CPU socket can be determined by parsing the file /proc/cpuinfo. The naming convention for the logical cores is: C{x.y.z} = hyper-thread z of physical core y of CPU socket x, with typical values of x = 0 .. 3, y = 0 .. 7, z = 0 .. 1. Logical cores C{0.0.1} and C{0.0.1} should be avoided while executing the test, as they are used by the Linux kernel for running regular processes.

  4. Software application requirements

  • Routing table for IPv4 packets
    • In LPM mode, the LPM table used for packet routing is:
    # LPM prefix (IP/length) Output port
    0 10.100.0.0/24 P1
    1 10.101.0.0/24 P1
    2 11.100.0.0/24 P2
    3 11.101.0.0/24 P2
    4 12.100.0.0/24 P3
    5 12.101.0.0/24 P3
    6 13.100.0.0/24 P4
    7 13.101.0.0/24 P4
    • In EM mode, the EM table used for packet routing is:
    Entry
    #
    		 IPv4 destination address IPv4 source address Port destination Port source L4 protocol Output port
    0 10.100.0.1 1.2.3.4 10 1 UDP P1
    1 10.101.0.1 1.2.3.4 10 1 UDP P1
    2 11.100.0.1 1.2.3.4 11 1 UDP P2
    3 11.101.0.1 1.2.3.4 11 1 UDP P2
    4 12.100.0.1 1.2.3.4 12 1 UDP P3
    5 12.101.0.1 1.2.3.4 12 1 UDP P3
    6 13.100.0.1 1.2.3.4 13 1 UDP P0
    7 13.101.0.1 1.2.3.4 13 1 UDP P0
  • Routing table for IPv6 packets
    • In LPM mode, the LPM table used for packet routing is:
    # LPM prefix (IPv6) Output port
    0 1:1:1:1:1:1:0:0 P0
    1 1:1:1:1:1:1:0:1 P0
    2 2:1:1:1:1:1:0:0 P1
    3 2:1:1:1:1:1:0:1 P1
    4 3:1:1:1:1:1:0:0 P2
    5 3:1:1:1:1:1:0:1 P2
    6 4:1:1:1:1:1:0:0 P3
    7 4:1:1:1:1:1:0:1 P3
    • In EM mode, the EM table used for packet routing is:
    Entry IPv6 destination address IPv6 source address Port destination Port source L4 protocol Output port
    0
    fe80:0000:0000:0000:021b:
    21ff:fe91:3805
    fe80:0000:0000:0000:021e:
    67ff:fe0d:b60a
    		 10 1 UDP P0
    1
    fe80:0000:0000:0000:021b:
    21ff:fe91:3805
    fe80:0000:0000:0000:021e:
    67ff:fe0d:b60a
    		 10 1 UDP P0
    2
    2a80:0000:0000:0000:021b:
    21ff:fe91:3805
    fe80:0000:0000:0000:021e:
    67ff:fe0d:b60a
    		 11 1 UDP P1
    3
    2a80:0000:0000:0000:021b:
    21ff:fe91:3805
    fe80:0000:0000:0000:021e:
    67ff:fe0d:b60a
    		 11 1 UDP P1
    4
    2b80:0000:0000:0000:021b:
    21ff:fe91:3805
    fe80:0000:0000:0000:021e:
    67ff:fe0d:b60a
    		 12 1 UDP P2
    5
    2b80:0000:0000:0000:021b:
    21ff:fe91:3805
    fe80:0000:0000:0000:021e:
    67ff:fe0d:b60a
    		 12 1 UDP P2
    6
    2c80:0000:0000:0000:021b:
    21ff:fe91:3805
    fe80:0000:0000:0000:021e:
    67ff:fe0d:b60a
    		 13 1 UDP P3
    7
    2c80:0000:0000:0000:021b:
    21ff:fe91:3805
    fe80:0000:0000:0000:021e:
    67ff:fe0d:b60a
    		 13 1 UDP P3
  1. Traffic generator requirements

The flows need to be configured and started by the traffic generator:

  • IPv4 packets
Flow Traffic Gen. Port IPv4 Src. Address IPv4 Dst. Address Port Src. Port Dest. L4 Proto. NIC RX Queue (RSS)
1 TG0 10.100.0.1 1.2.3.4 10 1 UDP 0
2 TG0 10.101.0.1 1.2.3.4 10 1 UDP 1
3 TG1 11.100.0.1 1.2.3.4 11 1 UDP 0
4 TG1 11.101.0.1 1.2.3.4 11 1 UDP 1
5 TG2 12.100.0.1 1.2.3.4 12 1 UDP 0
6 TG2 12.101.0.1 1.2.3.4 12 1 UDP 1
7 TG3 13.100.0.1 1.2.3.4 13 1 UDP 0
8 TG3 13.101.0.1 1.2.3.4 13 1 UDP 1
  • IPv6 packets
Entry
Traffic Gen.
Port
IPv6 Src address
address
IPv6 Dest address
address
 Port Src. Port Dest. L4 Proto.
RX Queue
(RSS)
1 TG0 1:1:1:1:1:1:0:0 1:2:3:4:5:6:7:8 10 1 UDP 0
2 TG0 1:1:1:1:1:1:0:1 1:2:3:4:5:6:7:8 10 1 UDP 1
3 TG1 2:1:1:1:1:1:0:0 1:2:3:4:5:6:7:8 11 1 UDP 0
4 TG1 2:1:1:1:1:1:0:1 1:2:3:4:5:6:7:8 11 1 UDP 1
5 TG2 3:1:1:1:1:1:0:0 1:2:3:4:5:6:7:8 12 1 UDP 0
6 TG2 3:1:1:1:1:1:0:1 1:2:3:4:5:6:7:8 12 1 UDP 1
7 TG3 4:1:1:1:1:1:0:0 1:2:3:4:5:6:7:8 13 1 UDP 0
8 TG3 4:1:1:1:1:1:0:1 1:2:3:4:5:6:7:8 13 1 UDP 1

The queue column represents the expected NIC port RX queue where the packet should be written by the NIC hardware when RSS is enabled for that port.

89.2. Test Case: Layer-3 Forwarding (in EM/LPM Mode) with IPv4/IPv6 Packets

The following items are configured through the command line interface of the application:

  • The set of one or several RX queues to be enabled for each NIC port
  • The set of logical cores to execute the packet forwarding task
  • Mapping of the NIC RX queues to logical cores handling them.

The test report should provide the throughput rate measurements (in mpps and % of the line rate for 4x NIC ports) as listed in the table below:

  Number of RX Queues per NIC Port Total Number of NIC RX Queues Number of Sockets/ Cores/Threads Total Number of Threads Number of NIX RX Queues per Thread Throughput Rate LPM Mode Throughput Rate EM Mode
mpps | % mpps | %
1 1 4 1S/1C/1T 1 4    

2 1 4 1S/1C/2T 2 2        
3 1 4 1S/2C/2T 2 2        
4 1 4 1S/2C/2T 4 1        
5 1 4 1S/4C/1T 4 1        
6 1 4 2S/1C/1T 2 2        
7 1 4 2S/1C/2T 4 1        
8 1 4 2S/2C/1T 4 1        
9 2 8 1S/1C/1T 1 8        
10 2 8 1S/1C/2T 2 4        
11 2 8 1S/2C/1T 2 4        
12 2 8 1S/2C/2T 4 2        
13 2 8 1S/4C/1T 4 2        
14 2 8 1S/4C/2T 8 1        
15 2 8 2S/1C/1T 2 4        
16 2 8 2S/1C/2T 4 2        
17 2 8 2S/2C/1T 4 2        
18 2 8 2S/2C/2T 8 1        
19 2 8 2S/4C/1T 8 1        

The application command line associated with each of the above tests is presented in the table below. The test report should present this table with the actual command line used, replacing the PORTMASK and C{x.y.z} with their actual values used during test execution.

# Command Line
1 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P1,0,C{0.1.0}),(P2,0,C{0.1.0}),(P3,0,C{0.1.0})’
2 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P1,0,C{0.1.0}),(P2,0,C{0.1.1}),(P3,0,C{0.1.1})’
3 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P1,0,C{0.1.0}),(P2,0,C{0.2.0}),(P3,0,C{0.2.0})’
4 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P1,0,C{0.1.1}),(P2,0,C{0.2.0}),(P3,0,C{0.2.1})’
5 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P1,0,C{0.2.0}),(P2,0,C{0.3.0}),(P3,0,C{0.4.0})’
6 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P1,0,C{0.1.0}),(P2,0,C{1.1.0}),(P3,0,C{1.1.0})’
7 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P1,0,C{0.1.1}),(P2,0,C{1.1.0}),(P3,0,C{1.1.1})’
8 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P1,0,C{0.2.0}),(P2,0,C{1.1.0}),(P3,0,C{1.2.0})’
9 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P0,1,C{0.1.0}),(P1,0,C{0.1.0}),(P1,1,C{0.1.0}), (P2,0,C{0.1.0}),(P2,1,C{0.1.0}),(P3,0,C{0.1.0}),(P3,1,C{0.1.0})’
10 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P0,1,C{0.1.0}),(P1,0,C{0.1.0}),(P1,1,C{0.1.0}), (P2,0,C{0.1.1}),(P2,1,C{0.1.1}),(P3,0,C{0.1.1}),(P3,1,C{0.1.1})’
11 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P0,1,C{0.1.0}),(P1,0,C{0.1.0}),(P1,1,C{0.1.0}), (P2,0,C{0.2.0}),(P2,1,C{0.2.0}),(P3,0,C{0.2.0}),(P3,1,C{0.2.0})’
12 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P0,1,C{0.1.0}),(P1,0,C{0.1.1}),(P1,1,C{0.1.1}), (P2,0,C{0.2.0}),(P2,1,C{0.2.0}),(P3,0,C{0.2.1}),(P3,1,C{0.2.1})’
13 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P0,1,C{0.1.0}),(P1,0,C{0.2.0}),(P1,1,C{0.2.0}), (P2,0,C{0.3.0}),(P2,1,C{0.3.0}),(P3,0,C{0.4.0}),(P3,1,C{0.4.0})’
14 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P0,1,C{0.1.1}),(P1,0,C{0.2.0}),(P1,1,C{0.2.1}), (P2,0,C{0.3.0}),(P2,1,C{0.3.1}),(P3,0,C{0.4.0}),(P3,1,C{0.4.1})’
15 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P0,1,C{0.1.0}),(P1,0,C{0.1.0}),(P1,1,C{0.1.0}), (P2,0,C{1.1.0}),(P2,1,C{1.1.0}),(P3,0,C{1.1.0}),(P3,1,C{1.1.0})’
16 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P0,1,C{0.1.0}),(P1,0,C{0.1.1}),(P1,1,C{0.1.1}), (P2,0,C{1.1.0}),(P2,1,C{1.1.0}),(P3,0,C{1.1.1}),(P3,1,C{1.1.1})’
17 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P0,1,C{0.1.0}),(P1,0,C{0.2.0}),(P1,1,C{0.2.0}), (P2,0,C{1.1.0}),(P2,1,C{1.1.0}),(P3,0,C{1.2.0}),(P3,1,C{1.2.0})’
18 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P0,1,C{0.1.1}),(P1,0,C{0.2.0}),(P1,1,C{0.2.1}), (P2,0,C{1.1.0}),(P2,1,C{1.1.1}),(P3,0,C{1.2.0}),(P3,1,C{1.2.1})’
19 ./dpdk-l3fwd -c 0xffffff -n 3 – -P -p PORTMASK –config ‘(P0,0,C{0.1.0}),(P0,1,C{0.2.0}),(P1,0,C{0.3.0}),(P1,1,C{0.4.0}), (P2,0,C{1.1.0}),(P2,1,C{1.2.0}),(P3,0,C{1.3.0}),(P3,1,C{1.4.0})’