Based on last weeks meeting, I've created a document to help start
documenting what test cases
should be worked on for cross platform support between NIC vendors and
which test cases can be used now in the Community Lab.
This list of test cases that should be worked on can be used when
discussing the budget with the board.
This also gives the Community Lab a list of tests that can be
implemented in the mean time.
https://docs.google.com/document/d/1WbRoIq0f5SmHM6D5sLbeh7hxRJdE2ppwB5JECHllLjg/edit?usp=sharing
(This document is publicly editable. If I notice the document changes
outside the scope of the goal, I'll try to revert it and give
individual access instead.)
If creating this list over email is wanted instead, then we can do it
in this thread instead of the document. (And I'll update the document
as emails come in.)
Well, for now, I prefer emails because I did not follow the CI discussions so far and I might be off topic.
Here I go, the list is large, I tried to write from the basic to the most advanced/less used.
- Non regression tests on basic startup (we can reuse the dpdk ut and/or enhance them), this part would be hw agnostic:
- core checks: playing with cpus online/offline + dpdk coremask/list + checking cpu affinity of all dpdk threads
- memory checks: a big topic because we have multiple modes at the moment
- startup devices blacklist/whitelist
- hotplug (unplug) of devices
- Non regression tests on eth drivers (testpmd seems the best candidate), this must be ran against a lot of nics/drivers:
- reception of unicast packets: check that we receive packets for primary and secondary addresses (and only for them, meaning with checks that undesired packets are dropped following updates)
- promisc support
- idem with multicast packets
- link status checks
- rte_eth_link_up/down checks
- mtu checks
- rss checks
- ptypes classification
- stats checks
- rte_flow checks
- port restart checks + associated configuration persistency
- flow control
- rx/tx offloads
- rx/tx descriptor status
--
David Marchand