From: Jason Terry <jason_terry@affirmednetworks.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] ACL Library Information Request
Date: Fri, 13 Nov 2015 15:17:24 +0000 [thread overview]
Message-ID: <BF39C1632926B849A8CC4705FA20425335A6CD69@MBX021-W3-CA-4.exch021.domain.local> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB97725836AC88AE@irsmsx105.ger.corp.intel.com>
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
prev parent reply other threads:[~2015-11-13 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 13:57 Jason Terry
2015-11-13 13:48 ` Ananyev, Konstantin
2015-11-13 15:17 ` Jason Terry [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BF39C1632926B849A8CC4705FA20425335A6CD69@MBX021-W3-CA-4.exch021.domain.local \
--to=jason_terry@affirmednetworks.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).