From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 38D6D6A80 for ; Tue, 14 Oct 2014 12:40:03 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 14 Oct 2014 03:47:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,716,1406617200"; d="scan'208";a="618301426" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by orsmga002.jf.intel.com with ESMTP; 14 Oct 2014 03:45:51 -0700 Received: from irsmsx109.ger.corp.intel.com (163.33.3.23) by IRSMSX103.ger.corp.intel.com (163.33.3.157) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 14 Oct 2014 11:45:50 +0100 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.174]) by IRSMSX109.ger.corp.intel.com ([169.254.13.253]) with mapi id 14.03.0195.001; Tue, 14 Oct 2014 11:45:50 +0100 From: "Ananyev, Konstantin" To: Karmarkar Suyash , "dev@dpdk.org" Thread-Topic: Bug in IPACL library of DPDK-1.6.0 Thread-Index: Ac/nlN/T4HWZL3EbQoWoKK2IGfS6ZQABrq6A Date: Tue, 14 Oct 2014 10:45:49 +0000 Message-ID: <2601191342CEEE43887BDE71AB9772582139376B@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.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "Dey, Souvik" , "Patil, PraveenKumar" Subject: Re: [dpdk-dev] Bug in IPACL library of DPDK-1.6.0 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, 14 Oct 2014 10:40:03 -0000 Hi, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Karmarkar Suyash > Sent: Tuesday, October 14, 2014 10:55 AM > To: dev@dpdk.org > Cc: Dey, Souvik; Patil, PraveenKumar > Subject: [dpdk-dev] Bug in IPACL library of DPDK-1.6.0 >=20 > Hello All, >=20 > If there are two identical IPv6 rules with source and destination IP addr= esses as wild card but with different priority, then during > lookup always the rule that is added first in TRIE is returned even thou= gh the second rule that has highest priority. >=20 Could you provide a bit more details how to reproduce the problem: - either a rule and trace file to reproduce the problem in testacl (classsb= ench) format -or some simple code snippet. Thanks Konstantin > Regards > Suyash Karmarkar