From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 555] Flow API issues with testpmd discovered during the creation of the rte flow test suite
Date: Wed, 14 Oct 2020 21:46:48 +0000 [thread overview]
Message-ID: <bug-555-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=555
Bug ID: 555
Summary: Flow API issues with testpmd discovered during the
creation of the rte flow test suite
Product: DPDK
Version: 20.08
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: ohilyard@iol.unh.edu
Target Milestone: ---
Created attachment 125
--> https://bugs.dpdk.org/attachment.cgi?id=125&action=edit
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.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-10-14 21:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-555-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).