154. ethtool stats

This document provides test plan for ethtool stats . This is a simple example app featuring packet processing, ethtool is a utility for Linux kernel-based operating system for displaying and modifying some parameters of network interface controllers (NICs) and their device drivers.

Currently Ethtool supports a more complete list of stats for the same drivers that DPDK supports. The idea behind this epic is two fold as following. 1. To achieve metric equivalence with what linux’s ethtool provides. 2. To extend the functionality of the xstats API to enable the following options:

- the retrieval of aggregate stats upon request (Top level stats).
- the retrieval of the extended NIC stats.
- grouping of stats logically so they can be retrieved per logical grouping.
- the option to enable/disable the stats groups to retrieve similar to set
  private flags in ethtool.

154.1. Prerequisites

2xNICs (2 full duplex optical ports per NIC). One on dut, another one on tester, link them together. Update two nics’ firmware to latest version:

  Tester                          DUT
.-------.                      .-------.
| port0 | <------------------> | port0 |
| port1 | <------------------> | port1 |
'-------'                      '-------'

154.2. Test cases

Check port extended statistics parameter after sending packet from peer link port.

bind two ports:

./usertools/dpdk-devbind.py --bind=igb_uio <pci address 1> <pci address 2>

154.2.1. Test Case: xstat options

check dpdk-procinfo tool support xstats command options.

These options should be included:

``xstats``
``xstats-name``
``xstats-id``
``xstats-reset``

steps:

  1. boot up testpmd:

    ./<target name>/app/testpmd -c 0x3 -n 4  -- -i --port-topology=loop
    
    testpmd> set fwd io
    testpmd> clear port xstats all
    testpmd> start
    
  2. run dpdk-procinfo tool:

    ./<target name>/app/dpdk-procinfo
    
  3. check dpdk-procinfo tool output should contain upper options.

154.2.2. Test Case: xstat statistic integrity

check if port extended statistics can access by xstat name or xstat id.

steps:

  1. boot up testpmd:

    ./<target name>/app/testpmd -c 0x3 -n 4  -- -i --port-topology=loop
    
    testpmd> set fwd io
    testpmd> clear port xstats all
    testpmd> start
    
  2. send udp packet of 64/72/128/256/512/1024 size to port 0/1:

    sendp([Ether()/IP()/UDP()/Raw('\0'*60)], iface=<port 0 name>)
    
  3. run dpdk-procinfo tool with xstats option and check if all ports extended statistics can access by xstat name or xstat id:

    ./<target name>/app/dpdk-procinfo -- -p 3 --xstats-id <N>
    ./<target name>/app/dpdk-procinfo -- -p 3 --xstats-name <statistic name>
    

154.2.3. Test Case: xstat-reset command

check if port extended statistics can be cleared.

steps:

  1. boot up testpmd:

    ./<target name>/app/testpmd -c 0x3 -n 4  -- -i --port-topology=loop
    
    testpmd> set fwd io
    testpmd> clear port xstats all
    testpmd> start
    
  2. send udp packet of 64/72/128/256/512/1024 size to port 0/1:

    sendp([Ether()/IP()/UDP()/Raw('\0'*60)], iface=<port 0 name>)
    
  3. run dpdk-procinfo tool with xstats-reset option and check if all port statistics have been cleared:

    ./<target name>/app/dpdk-procinfo -- -p 3 --xstats-reset
    

154.2.4. Test Case: xstat single statistic

check if port extended statistic name can be get by statistic id and check related data’s correctness with testpmd xstat data.

steps:

  1. boot up testpmd:

    ./<target name>/app/testpmd -c 0x3 -n 4  -- -i --port-topology=loop
    
    testpmd> set fwd io
    testpmd> clear port xstats all
    testpmd> start
    
  2. send udp packet of 64/72/128/256/512/1024 size to port 0/1:

    sendp([Ether()/IP()/UDP()/Raw('\0'*60)], iface=<port 0 name>)
    
  3. run test pmd show port xstats all to get testpmd port xstat data:

    testpmd> show port xstats all

  4. run dpdk-procinfo tool with xstats-id option to get the statistic name corresponding with the index id:

    ./<target name>/app/dpdk-procinfo -- -p 3 --xstats-id 0,1,...N
    
  5. run dpdk-procinfo tool with xstats-name option to get the statistic data corresponding with the statistic name:

    ./<target name>/app/dpdk-procinfo -- -p 3 --xstats-name <statistic name>
    
  6. compare these proc info tool xstat values with testpmd xstat values.