From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hub021-ca-3.exch021.serverdata.net (hub021-ca-3.exch021.serverdata.net [64.78.22.170]) by dpdk.org (Postfix) with ESMTP id 415EA941C for ; Fri, 13 Nov 2015 16:17:26 +0100 (CET) Received: from MBX021-W3-CA-4.exch021.domain.local ([10.254.4.80]) by HUB021-CA-3.exch021.domain.local ([10.254.4.36]) with mapi id 14.03.0224.002; Fri, 13 Nov 2015 07:17:24 -0800 From: Jason Terry To: "Ananyev, Konstantin" , "dev@dpdk.org" Thread-Topic: ACL Library Information Request Thread-Index: AdEdUhUutbQklm2dSyKfBtxID0DE5gAxtURgAANQaEA= Date: Fri, 13 Nov 2015 15:17:24 +0000 Message-ID: References: <2601191342CEEE43887BDE71AB97725836AC88AE@irsmsx105.ger.corp.intel.com> In-Reply-To: <2601191342CEEE43887BDE71AB97725836AC88AE@irsmsx105.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [50.205.79.154] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] ACL Library Information Request 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: Fri, 13 Nov 2015 15:17:26 -0000 Thanks! -----Original Message----- From: Ananyev, Konstantin [mailto:konstantin.ananyev@intel.com]=20 Sent: Friday, November 13, 2015 8:49 AM To: Jason Terry; dev@dpdk.org Subject: RE: ACL Library Information Request Hi Jason, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jason Terry > Sent: Thursday, November 12, 2015 1:58 PM > To: dev@dpdk.org > Subject: [dpdk-dev] ACL Library Information Request >=20 > HI, >=20 > I've read the documentation and looked at the example acl app. =20 > What is the best practice for deleting rules? The API looks like a new c= ontext needs created and built. Is that true? You don't have to create a new context, but you'll need to: delete all rules repopulate context with rules you'd like to keep build context. Or as you said - just create new context, populate it, build, destroy old o= ne. > Also, this is more of a confirmation, but RTE_ACL_MAX_FIELDS is=20 > defined as 64, so I assume that for ipv4 we can have a tuple that's large= r than 5? Yes, in theory up to 64 fields allowed, though on practice I never used mor= e than 11 so far. Konstantin >=20 > Thanks, > Jason