Test ingress to specific queue flow API rules

Verify Flow API by adding a filter and inspecting the inbound traffic

  1. Setup 2 Rx queues in non-RSS mode

  2. Prepare TEST_ETHDEV_INITIALIZED state

  3. Check maximum number of Rx queues

  4. Enter isolated mode if need be

  5. Prepare TEST_ETHDEV_STARTED state

  6. Ensure that interface is UP on Tester side

  7. Make flow rule attributes with only one "ingress" attribute

  8. Make flow rule pattern by flow_rule_pattern

  9. Make flow rule actions with only one "queue" action

  10. Validate and create the flow rule

  11. Prepare template that matches the filter

  12. Add tunnel UDP ports to recognize received packets if VXLAN/GENEVE protocols are used

  13. When filtering a multicast packet and a unicast packet with enabled promiscuous mode, it is expected that there will be a duplication of packets

  14. Enable promiscuous mode if need be

  15. Transmit and receive one packet with prepared match template. Check that the packet was received on correct queue.

  16. Transmit and receive packets with dissimilar templates. Check that packets were received on default queue.

Parameters:

flow_rule_in2q

Flow rule

isolated

Isolated mode toggle

promisc

Test with promiscuous mode enabled if TRUE