From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id E08545917 for ; Tue, 28 Oct 2014 12:42:41 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 28 Oct 2014 04:50:07 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,802,1406617200"; d="scan'208";a="626861517" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by orsmga002.jf.intel.com with ESMTP; 28 Oct 2014 04:51:26 -0700 Received: from irsmsx109.ger.corp.intel.com (163.33.3.23) by IRSMSX101.ger.corp.intel.com (163.33.3.153) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 28 Oct 2014 11:51:16 +0000 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.56]) by IRSMSX109.ger.corp.intel.com ([169.254.13.101]) with mapi id 14.03.0195.001; Tue, 28 Oct 2014 11:51:15 +0000 From: "Ananyev, Konstantin" To: Erik Ziegenbalg , "dev@dpdk.org" Thread-Topic: rte_acl test-acl app Thread-Index: AQHP8AJsh7S9oanRTkyco2O83gcY+JxFaPqA Date: Tue, 28 Oct 2014 11:51:15 +0000 Message-ID: <2601191342CEEE43887BDE71AB977258213A0D44@IRSMSX105.ger.corp.intel.com> References: In-Reply-To: Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] rte_acl test-acl app X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 11:42:42 -0000 Hi Erik, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Erik Ziegenbalg > Sent: Saturday, October 25, 2014 4:19 AM > To: dev@dpdk.org > Subject: [dpdk-dev] rte_acl test-acl app >=20 > Hi everyone, >=20 > I am having trouble to successfully perform a packet classification > using the rte_acl test app. I have my rules.acl and trace.acl files as > follows: >=20 > rules.acl: > @192.168.0.0/24 192.168.0.0/24 400 : 500 1000 : 2000 6/0xff >=20 > trace.acl: > 192.168.0.5 192.168.0.9 450 1002 0x06 >=20 > However, the result always comes up as 4294967295 (xFFFFFFFF). I have > dug through the code quite a bit to follow and see what is going on, but > not sure where I went wrong. >=20 > Any help on how the rte_acl_classify function works would be much > appreciated. In understand that the data for rte_acl_classify is a > uint32_t ** and I double checked to make sure I'm passing along proper > values. Is xFFFFFFFF the expected result? If so, I am getting the same > for packets that should not match. That's strange: for me latest code with dpdk.org works as expected: # cat ./test/rule1 @192.168.0.0/24 192.168.0.0/24 400 : 500 1000 : 2000 6/0xff # cat ./test/trace1 0xc0a80005 0xc0a80009 450 1002 0x06 # ./dpdk.org/x86_64-native-linuxapp-gcc/app/testacl -n 2 -c 4 -- --rules= f=3D./test/rule1 --tracef=3D./test/trace1 .... ipv4_5tuple: 1, category: 0, result: 0 ... i.e: rule #0 matches given flow, as expected.=20 Do you use testacl or some other app? Konstantin >=20 > Thank you, > Erik Ziegenbalg