From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 27DB9A00C5; Mon, 27 Apr 2020 17:10:03 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 6109F1D519; Mon, 27 Apr 2020 17:10:02 +0200 (CEST) Received: from smtp1.iitb.ac.in (smtpd8.iitb.ac.in [103.21.126.63]) by dpdk.org (Postfix) with ESMTP id D34771D454 for ; Mon, 27 Apr 2020 17:10:00 +0200 (CEST) Received: from ldns1.iitb.ac.in (ldns1.iitb.ac.in [10.200.12.1]) by smtp1.iitb.ac.in (Postfix) with SMTP id EC54D10102A3 for ; Mon, 27 Apr 2020 20:39:59 +0530 (IST) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.iitb.ac.in EC54D10102A3 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iitb.ac.in; s=mail; t=1588000199; bh=6+TGH13XNgPxeFxOJFWm/XDnR103+sKhCFxv+tE2Xgc=; h=Date:From:To:Cc:Subject:From; b=P1p2bZTNorRzWOJ28BAtTdUBatRLlg2NoKtEAlxkWggzEMqoPoZuAX950c+Oeix4x Sc5LrVaHu6Uxco035cu+U00AnQWWY8rKSQPl9uefOqwy03XB9mbns3ifOOMUb9C4BM sDZnFFW7r/lNvMzxOEWLI4mXwdc7mW/NXiigXY8s= Received: (qmail 10167 invoked by uid 510); 27 Apr 2020 20:39:59 +0530 X-Qmail-Scanner-Diagnostics: from 10.200.1.25 by ldns1 (envelope-from , uid 501) with qmail-scanner-2.11 spamassassin: 3.4.1. mhr: 1.0. {clamdscan: 0.101.4/25794} Clear:RC:1(10.200.1.25):SA:0(0.0/7.0):. Processed in 2.354694 secs; 27 Apr 2020 20:39:59 +0530 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on ldns1.iitb.ac.in X-Spam-Level: X-Spam-Status: No, score=0.0 required=7.0 tests=IITB_ORIG,PROPER_IITB_MSGID, T_RP_MATCHES_RCVD autolearn=disabled version=3.4.1 X-Spam-Pyzor: Reported 0 times. X-Envelope-From: diptyaroop@cse.iitb.ac.in X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received: from unknown (HELO ldns1.iitb.ac.in) (10.200.1.25) by ldns1.iitb.ac.in with SMTP; 27 Apr 2020 20:39:57 +0530 Received: from mail.cse.iitb.ac.in (miller.cse.iitb.ac.in [10.129.3.1]) by ldns1.iitb.ac.in (Postfix) with ESMTP id 37A1F360060 for ; Mon, 27 Apr 2020 20:39:57 +0530 (IST) Received: by mail.cse.iitb.ac.in (Postfix, from userid 5001) id 321A6F40C07; Mon, 27 Apr 2020 20:39:57 +0530 (IST) Received: from www.cse.iitb.ac.in (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by mail.cse.iitb.ac.in (Postfix) with ESMTPSA id E32E9F40C00; Mon, 27 Apr 2020 20:39:56 +0530 (IST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 27 Apr 2020 20:39:56 +0530 From: diptyaroop To: dev@dpdk.org Cc: Unhale Nilesh Arun Message-ID: <2907ba358106499b2c1af1961057d39e@cse.iitb.ac.in> X-Sender: diptyaroop@cse.iitb.ac.in User-Agent: Roundcube Webmail/1.3.9 Subject: [dpdk-dev] Flow action not supported in testpmd X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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