Hello Ori,
I work at the UNH-IOL DPDK Community Lab, and I am writing an rte_flow test suite to add to the DPDK Test Suite. The flow API allows for an extremely broad set of rules to be created. My understanding from my first pass at writing the test suite is that there is a small subset of those rules that are “core functionality” that the flow API aims to support, and there are also rules which technically can be created, but may not be supported by the main PMDs and/or may not be useful rules that people want to see tested. For instance, I am pretty confident that a rule like the one below is one which the community will care about, and which PMDs will support: flow create 0 ingress pattern eth / ipv4 src is 192.168.0.1 / end actions drop / end But I do not know what is the full set of rules that I should be validating from a DTS testsuite. Is it possible for you (or anyone else on this mailing list) to provide some feedback on what rules are most important and I should include in my test suite? If I can get that feedback, I will draft a test plan and share it back on this thread for community approval before I write up and submit the DTS patch. Thanks for your time, Dean Marx
