From: diptyaroop <diptyaroop@cse.iitb.ac.in>
To: dev@dpdk.org
Cc: Unhale Nilesh Arun <nileshunhale@cse.iitb.ac.in>
Subject: [dpdk-dev] Flow action not supported in testpmd
Date: Mon, 27 Apr 2020 20:39:56 +0530 [thread overview]
Message-ID: <2907ba358106499b2c1af1961057d39e@cse.iitb.ac.in> (raw)
Hello,
I am trying to check different flow rules using testpmd (DPDK v19.11), but
facing the following error for any rule that I try:
testpmd> flow validate 0 ingress pattern eth / end actions queue index 6 /
end
port_flow_complain(): Caught PMD error type 16 (specific action): cause:
0x7ffe62373c18, Not supported action.: Invalid argument
testpmd> flow validate 1 ingress pattern eth / end actions queue index 6 /
end
port_flow_complain(): Caught PMD error type 16 (specific action): cause:
0x7ffe62373c18, Not supported action.: Invalid argument
testpmd>
testpmd>
testpmd> flow validate 1 ingress pattern end actions end
port_flow_complain(): Caught PMD error type 16 (specific action): cause:
0x7ffe62373bf8, Not supported action.: Invalid argument
testpmd> flow validate 1 pattern end actions end
port_flow_complain(): Caught PMD error type 16 (specific action): cause:
0x7ffe62373bf8, Not supported action.: Invalid argument
testpmd> flow validate 1 ingress pattern eth / ipv4 / end actions end
port_flow_complain(): Caught PMD error type 16 (specific action): cause:
0x7ffe62373c38, Not supported action.: Invalid argument
testpmd> flow validate 1 ingress pattern eth / ipv4 / end actions drop / end
port_flow_complain(): Caught PMD error type 16 (specific action): cause:
0x7ffe62373c38, Not supported action.: Invalid argument
I have configured 8 rxqs earlier:
testpmd> show config rxtx
io packet forwarding packets/burst=32
nb forwarding cores=1 - nb forwarding ports=2
port 0: RX queue number: 8 Tx queue number: 8
Rx offloads=0x0 Tx offloads=0x0
RX queue: 0
RX desc=1024 - RX free threshold=32
RX threshold registers: pthresh=8 hthresh=8 wthresh=0
RX Offloads=0x0
TX queue: 0
TX desc=1024 - TX free threshold=32
TX threshold registers: pthresh=32 hthresh=0 wthresh=0
TX offloads=0x0 - TX RS bit threshold=32
port 1: RX queue number: 8 Tx queue number: 8
Rx offloads=0x0 Tx offloads=0x0
RX queue: 0
RX desc=1024 - RX free threshold=32
RX threshold registers: pthresh=8 hthresh=8 wthresh=0
RX Offloads=0x0
TX queue: 0
TX desc=1024 - TX free threshold=32
TX threshold registers: pthresh=32 hthresh=0 wthresh=0
TX offloads=0x0 - TX RS bit threshold=32
Kindly let me know if I am doing anything wrong or if my NIC does not support
rte_flow.
Also, is there any resource available where I can find which patterns/actions
are supported in my NIC (for DPDK v19.11)?
I am trying to develop an application which will match GTP packets and
perform decap + queue action on them.
Configuration:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 24
On-line CPU(s) list: 0-23
Thread(s) per core: 1
Core(s) per socket: 12
Socket(s): 2
NUMA node(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 79
Model name: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
NIC: 03:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
03:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
Thanks and Regards,
Diptyaroop Maji
Department of CSE
IIT Bombay
reply other threads:[~2020-04-27 15:10 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=2907ba358106499b2c1af1961057d39e@cse.iitb.ac.in \
--to=diptyaroop@cse.iitb.ac.in \
--cc=dev@dpdk.org \
--cc=nileshunhale@cse.iitb.ac.in \
/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).