DPDK Test Plans
stable
  • 1. Port Blacklist Tests
  • 2. RX/TX Checksum Offload Tests
  • 3. Cloud filter Support through Ethtool Tests
  • 4. Coremask Tests
  • 5. Cryptodev Performance Application Tests
  • 6. Fortville DDP (Dynamic Device Personalization) Tests
  • 7. Dual VLAN Offload Tests
  • 8. Dynamic Driver Configuration Tests
  • 9. External Tag (E-tag) Tests
  • 10. External Mempool Handler Tests
  • 11. Niantic Flow Director Tests
  • 12. VEB Switch and floating VEB Tests
  • 13. Fortville Granularity Configuration of RSS and 32-bit GRE key Tests
  • 14. FM10k FTAG Forwarding Tests
  • 15. Generic Filter Tests
  • 16. DPDK Hotplug API Tests
  • 17. IEEE1588 Precise Time Protocol Tests
  • 18. One-shot Rx Interrupt Tests
  • 19. IP fragmentation Tests
  • 20. Generic Routing Encapsulation (GRE) Tests
  • 21. IP Pipeline Application Tests
  • 22. IP Reassembly Tests
  • 23. Jumbo Frame Tests
  • 24. Kernel NIC Interface (KNI) Tests
  • 25. CryptoDev API Tests
  • 26. L2 Forwarding Tests
  • 27. L3 Forwarding Exact Match Tests
  • 28. L3 Forwarding Tests
  • 29. Ethernet Link Flow Control Tests
  • 30. Link Status Detection Tests
    • 30.1. Prerequisites
    • 30.2. Test Case: Link Status Change
    • 30.3. Test Case: Port available
  • 31. Whitelisting Tests
  • 32. Niantic Media Access Control Security (MACsec) Tests
  • 33. External Mempool Handler Tests
  • 34. NIC Statistics Tests
  • 35. Fortville NVGRE Tests
  • 36. Bonding Tests
  • 37. TestPMD PCAP Tests
  • 38. Fortville RSS - Configuring Hash Function Tests
  • 39. Niantic Reta (Redirection table) Tests
  • 40. Niantic PMD Tests
  • 41. PTYPE Mapping Tests
  • 42. Shutdown API Queue Tests
  • 43. Scattered Packets Tests
  • 44. Short-lived Application Tests
  • 45. Shutdown API Feature Tests
  • 46. SRIOV and InterVM Communication Tests
  • 47. Stability Tests
  • 48. Transmit Segmentation Offload (TSO) Tests
  • 49. Tx Preparation Forwarding Tests
  • 50. Unified Packet Type Tests
  • 51. Userspace Ethtool Tests
  • 52. VEB Switch and floating VEB Tests
  • 53. VFD as SRIOV Policy Manager Tests
  • 54. VF Jumboframe Tests
  • 55. VF One-shot Rx Interrupt Tests
  • 56. VF MAC Filter Tests
  • 57. VF Offload
  • 58. VF Packet RxTX Tests
  • 59. VF PF Reset Tests
  • 60. VF Port Start Stop Tests
  • 61. VF RSS - Configuring Hash Function Tests
  • 62. VF to VF Bridge Tests
  • 63. VF VLAN Tests
  • 64. Vhost PMD Xstats Tests
  • 65. Vhost TSO Tests
  • 66. Vhost User Live Migration Tests
  • 67. Virtio-1.0 Support Tests
  • 68. VLAN Ethertype Config Tests
  • 69. VLAN Offload Tests
  • 70. VMDQ Tests
  • 71. VM Power Management Tests
  • 72. Fortville Vxlan Tests
  • 73. Niantic ixgbe_get_vf_queue Include Extra Information Tests
  • 74. Fortville Configure RSS Queue Regions Tests
  • 75. Niantic Inline IPsec Tests
  • 76. Eventdev Pipeline SW PMD Tests
  • 77. Fortville Dynamic Mapping of Flow Types to PCTYPEs Tests
  • 78. VFD as SRIOV Policy Manager Tests
  • 79. Multiple Pthread Test
  • 80. Fortville Cloud filters for QinQ steering Tests
  • 81. Fortville DDP GTP-C/GTP-U Tests
  • 82. Generic filter/flow api
  • 83. DDP GTP Qregion
  • 84. Dynamically Configure VF Queue Number
  • 85. Vhost/Virtio multiple queue qemu test plan
  • 86. Vhost MTU Test Plan
  • 87. Unit Tests: Cmdline
  • 88. Unit Tests: CRC
  • 89. Unit Tests: Cryptodev
  • 90. Unit Tests: Dump Log History
  • 91. Unit Tests: Dump Ring
  • 92. Unit Tests: Dump Mempool
  • 93. Unit Tests: Dump Physical Memory
  • 94. Unit Tests: Dump Memzone
  • 95. Unit Tests: Dump Struct Size
  • 96. Unit Tests: EAL
  • 97. Unit Tests: KNI
  • 98. Unit Tests: LPM
  • 99. Unit Tests: LPM_ipv6
  • 100. Unit Tests: Mbuf
  • 101. Unit Tests: Mempool
  • 102. Unit Tests: PMD Performance
  • 103. Unit Tests: Power Library
  • 104. Unit Tests: Random Early Detection (RED)
  • 105. Unit Tests: Metering
  • 106. Unit tests: Scheduler
  • 107. Unit Tests: Ring Pmd
  • 108. Unit Tests: Ring
  • 109. Unit Tests: Ring Performance
  • 110. Unit tests: Timer
  • 111. Sample Application Tests: Cmdline Example
  • 112. Sample Application Tests: Hello World Example
  • 113. Sample Application Tests: Keep Alive Example
  • 114. Sample Application Tests: Multi-Process
  • 115. Sample Application Tests: Netmap Compatibility
  • 116. Sample Application Tests: Quota and Water-mark
  • 117. Sample Application Tests: RX/TX Callbacks
  • 118. Sample Application Tests: Basic Forwarding/Skeleton Application
  • 119. Sample Application Tests: Timer Example
  • 120. Sample Application Tests: Vxlan Example
  • 121. Sample Application Tests: IEEE1588
  • 122. Sample Application Tests: Packet distributor
  • 123. Sample Application Tests: Elastic Flow Distributor
DPDK Test Plans
  • Docs »
  • 30. Link Status Detection Tests
  • View page source

30. Link Status Detection Tests¶

This tests for Detect Link Status feature can be run on linux userspace. It is to check if the userspace interrupt can be received after plugging in/out the cable/fiber on specified NIC port, and if the link status can be updated correctly. Furthermore, it would be better to check if packets can be received and sent on a specified port after its link has just up. So it may need layer 2 forwarding at the same time.

For layer 2 forwarding, a packet received on a RX port (RX_PORT), it would be transmitted from a TX port (TX_PORT=RX_PORT+1) if RX_PORT is even; otherwise from a TX port (TX_PORT=RX_PORT-1) if RX_PORT is odd. Before being transmitted, the source mac address of the packet would be replaced by the mac address of the TX port, while the destination mac address would be replaced by 00:09:c0:00:00:TX_PORT_ID. The test application should be run with the wanted paired ports configured using the coremask parameter via the command line. i.e. port 0 and 1 is a valid pair, while port 1 and 2 isn’t. The test is performed by running the test application and using a traffic generator.

The link_status_interrupt application is run with EAL parameters and parameters for the application itself. This application supports three parameters for itself.

  • -p PORTMASK: hexadecimal bitmask of ports to config
  • -q NQ: number of queue per lcore (default is 1)
  • -T PERIOD: refresh period in seconds (0/10/86400: disable/default/maximum)

30.1. Prerequisites¶

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

The test app need add a cmdline, --vfio-intr=int_x.

Assume port 0 and 1 are connected to the remote ports, e.g. packet generator. To run the test application in linuxapp environment with 4 lcores, 2 ports and 2 RX queues per lcore:

$ ./link_status_interrupt -c f -- -q 2 -p 0x3

Also, if the ports need to be tested are different, the port mask should be changed. The lcore used to run the test application and the number of queues per lcore could be changed.

30.2. Test Case: Link Status Change¶

Run the test application as above command. Then plug out the cable/fiber, or simulate a disconnection. After several seconds, check if the link is actually off. Then plug in the cable/fiber, or simulate a connection. After several seconds, check if the link is actually up, and print its information about duplex and speed.

30.3. Test Case: Port available¶

Run the test application as above command with cable/fiber plugged out from both port 0 and 1, then plug it in. After several seconds and the link of all the ports is up. Together with packet generator, do layer 2 forwarding, and check if the packets can be received on port 0/1 and sent out on port 1/0.

Next Previous

© Copyright 2017, dpdk.org. Revision a7c8df3d.

Built with Sphinx using a theme provided by Read the Docs.