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 04AD9255 for ; Wed, 28 Jan 2015 12:11:15 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 28 Jan 2015 03:08:00 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,480,1418112000"; d="scan'208";a="643778522" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by orsmga001.jf.intel.com with ESMTP; 28 Jan 2015 03:11:14 -0800 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.81]) by IRSMSX153.ger.corp.intel.com ([169.254.9.2]) with mapi id 14.03.0195.001; Wed, 28 Jan 2015 11:11:12 +0000 From: "Ananyev, Konstantin" To: "Rapelly, Varun" , "dev@dpdk.org" Thread-Topic: ACL trie insertion and search Thread-Index: AdA6sIuqLTOjGBB+R4StoW6g/V92KwAKT2twAAQwZxA= Date: Wed, 28 Jan 2015 11:11:12 +0000 Message-ID: <2601191342CEEE43887BDE71AB977258213E0099@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.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] ACL trie insertion and search 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: Wed, 28 Jan 2015 11:11:16 -0000 Hi > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Rapelly, Varun > Sent: Wednesday, January 28, 2015 9:07 AM > To: dev@dpdk.org > Subject: [dpdk-dev] ACL trie insertion and search >=20 > Hi, >=20 > We were converting the acl rule data, from host to network byte order, [b= y mistake] while inserting into trie. And while searching we > are not converting the search data to n/w byte order. > With the above also rules are matching, except few scenarios. >=20 > After correcting the above mistake, all rules are matching perfectly fine= . >=20 > I believe the above[converting while insertion] should also work for all = rules. Please clarify the above. Yes, that's correct. rte_acl_add_rules() expects all fields to be in host byte order, while rte_acl_classify()expects all fields in input data buffers to be in network= byte order. As mentioned in comments in rte_acl.h. =20 Konstantin >=20 > Regards, > Varun