[dpdk-dev] ACL Library Information Request
Jason Terry
jason_terry at affirmednetworks.com
Fri Nov 13 16:17:24 CET 2015
Thanks!
-----Original Message-----
From: Ananyev, Konstantin [mailto:konstantin.ananyev at intel.com]
Sent: Friday, November 13, 2015 8:49 AM
To: Jason Terry; dev at dpdk.org
Subject: RE: ACL Library Information Request
Hi Jason,
> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jason Terry
> Sent: Thursday, November 12, 2015 1:58 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] ACL Library Information Request
>
> HI,
>
> I've read the documentation and looked at the example acl app.
> What is 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
repopulate context with rules you'd like to keep build context.
Or as you said - just create new context, populate it, build, destroy old one.
> 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 more than 11 so far.
Konstantin
>
> Thanks,
> Jason
More information about the dev
mailing list