Bug 555
| Summary: | Flow API issues with testpmd discovered during the creation of the rte flow test suite | ||
|---|---|---|---|
| Product: | DPDK | Reporter: | Owen Hilyard (ohilyard) |
| Component: | examples | Assignee: | jeffguo (jia.guo) |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | ajit.khaparde |
| Priority: | Normal | ||
| Version: | 20.08 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Attachments: | The log from the test suite as well as a list of failed tests and what caused them to fail. | ||
Jeff, Can you please check? From what I can see, this seems to be an issue with i40e PMD. hi, owen and ajit For the attach test suite, some case is not support eventually. We just plan and progress to refactor the rte flow api in i40e for 21.02, and seems that we also need to add some manifest or doc to show what ptype we support what we don't support, so please expected this issue be fixed target to 21.02, we will arrange guys to fix it. |
Created attachment 125 [details] The log from the test suite as well as a list of failed tests and what caused them to fail. While working on the rte flow test case, I found that there are quite a few places where "flow validate" will pass for a statement, only for "flow create" to fail. I also found a few places where rules do not seem to applying their actions to a matching packet, or were applying actions to non-matching packets. All of the flow syntax is based off of the rte flow programmer's guide.