From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <konstantin.ananyev@intel.com>
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24])
 by dpdk.org (Postfix) with ESMTP id 378B09426
 for <dev@dpdk.org>; Fri, 13 Nov 2015 14:48:46 +0100 (CET)
Received: from orsmga002.jf.intel.com ([10.7.209.21])
 by orsmga102.jf.intel.com with ESMTP; 13 Nov 2015 05:48:46 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.20,287,1444719600"; d="scan'208";a="849799517"
Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155])
 by orsmga002.jf.intel.com with ESMTP; 13 Nov 2015 05:48:44 -0800
Received: from irsmsx111.ger.corp.intel.com (10.108.20.4) by
 IRSMSX102.ger.corp.intel.com (163.33.3.155) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Fri, 13 Nov 2015 13:48:43 +0000
Received: from irsmsx105.ger.corp.intel.com ([169.254.7.203]) by
 irsmsx111.ger.corp.intel.com ([169.254.2.223]) with mapi id 14.03.0248.002;
 Fri, 13 Nov 2015 13:48:43 +0000
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Jason Terry <jason_terry@affirmednetworks.com>, "dev@dpdk.org"
 <dev@dpdk.org>
Thread-Topic: ACL Library Information Request
Thread-Index: AdEdUhUutbQklm2dSyKfBtxID0DE5gAxtURg
Date: Fri, 13 Nov 2015 13:48:42 +0000
Message-ID: <2601191342CEEE43887BDE71AB97725836AC88AE@irsmsx105.ger.corp.intel.com>
References: <BF39C1632926B849A8CC4705FA20425335A6C548@MBX021-W3-CA-4.exch021.domain.local>
In-Reply-To: <BF39C1632926B849A8CC4705FA20425335A6C548@MBX021-W3-CA-4.exch021.domain.local>
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 Library Information Request
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Nov 2015 13:48:46 -0000

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.  What i=
s the best practice for deleting rules?  The API looks like a
> new context needs created and built.  Is that true?

You don't have to create a new context, but you'll need to:
delete all rules=20
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 defined =
as 64, so
> I assume that for ipv4 we can have a tuple that's larger 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