From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 449] Fortville X710 FDIR with flow APIs broken
Date: Mon, 13 Apr 2020 11:42:27 +0000 [thread overview]
Message-ID: <bug-449-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=449
Bug ID: 449
Summary: Fortville X710 FDIR with flow APIs broken
Product: DPDK
Version: 20.02
Hardware: x86
URL: https://doc.dpdk.org/dts/test_plans/generic_flow_api_t
est_plan.html
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: eventdev
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
DPDK version tested: 19.11.1 & 20.2
section: 28.5, Flow config for VF-0 for ipv4-other
Rule:
1. `flow create 0 ingress pattern eth / ipv4 src is 192.168.0.1 dst is
192.168.0.2 proto is 3 / vf id is 0 / end actions queue index 1 / end`
2. `flow create 0 ingress pattern eth / ipv4 src is 11.11.11.11 dst is
12.12.12.12 proto is 17 / vf id is 0 / end actions queue index 1 / end`
3. `flow create 0 ingress pattern eth / ipv4 proto is 17 / vf id is 0 / end
actions queue index 1 / end`
Result: `Caught error type 13 (specific pattern item): cause: 0x17ff5b140,
Matching VF traffic without affecting it (transfer attribute) is unsupported:
Operation not supported`
CMD:
a. PF: ``` ./x86_64-native-linuxapp-gcc/app/testpmd -l 14-15 -w 08:00.0
--socket-mem=128 -- -i --rxq=4 --txq=4 --disable-rss
--pkt-filter-mode=perfect```
b. VF: ```./x86_64-native-linuxapp-gcc/app/testpmd -l 16-17 -w 0000:08:02.0
--socket-mem=128,0 --file-prefix=vf -- -i --rxq=4 --txq=4 --disable-rss
--pkt-filter-mode=perfect```
on both:
```
set fwd rxonly
set verbose 1
start
```
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-04-13 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 11:42 bugzilla [this message]
2020-12-30 6:19 ` bugzilla
2021-01-04 3:15 ` bugzilla
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-449-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).