* [dpdk-dev] ACL Library Information Request
@ 2015-11-12 13:57 Jason Terry
2015-11-13 13:48 ` Ananyev, Konstantin
0 siblings, 1 reply; 3+ messages in thread
From: Jason Terry @ 2015-11-12 13:57 UTC (permalink / raw)
To: dev
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? 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?
Thanks,
Jason
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] ACL Library Information Request
2015-11-12 13:57 [dpdk-dev] ACL Library Information Request Jason Terry
@ 2015-11-13 13:48 ` Ananyev, Konstantin
2015-11-13 15:17 ` Jason Terry
0 siblings, 1 reply; 3+ messages in thread
From: Ananyev, Konstantin @ 2015-11-13 13:48 UTC (permalink / raw)
To: Jason Terry, dev
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
>
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] ACL Library Information Request
2015-11-13 13:48 ` Ananyev, Konstantin
@ 2015-11-13 15:17 ` Jason Terry
0 siblings, 0 replies; 3+ messages in thread
From: Jason Terry @ 2015-11-13 15:17 UTC (permalink / raw)
To: Ananyev, Konstantin, dev
Thanks!
-----Original Message-----
From: Ananyev, Konstantin [mailto:konstantin.ananyev@intel.com]
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
>
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-11-13 15:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-11-12 13:57 [dpdk-dev] ACL Library Information Request Jason Terry
2015-11-13 13:48 ` Ananyev, Konstantin
2015-11-13 15:17 ` Jason Terry
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).