From: "Gowda, Deepak" <dgowda@rbbn.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK ACL Trie
Date: Tue, 30 Jul 2019 01:17:20 -0400 [thread overview]
Message-ID: <BN6PR03MB26109169EDC23DBECBC14128B7DC0@BN6PR03MB2610.namprd03.prod.outlook.com> (raw)
Hi,
I'm experimenting on DPDK trie for ACL implementation. It turns out the more the number of rules, the more time rte_acl_build() takes which is expected. But, I was wondering if there are any standard benchmarking data that indicates build time for 'x' number of rules.
I benchmarked it myself, the build time for a few hundred rules is quite large really. It's in the order of secs, I can't help but think how could this happen, I mean in networking we typically can't afford 'seconds' of delay right.?
I just want to recheck my data against yours (if any) just to be sure.
With trie build-time being the constraint, I'm unable to scale up the no. of ACLs.
Hoping to see my query answered.
Thanks,
Deepak Gowda
-----------------------------------------------------------------------------------------------------------------------
Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. that
is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or
distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended
recipient, please notify the sender immediately and then delete all copies, including any attachments.
-----------------------------------------------------------------------------------------------------------------------
reply other threads:[~2019-07-30 12:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BN6PR03MB26109169EDC23DBECBC14128B7DC0@BN6PR03MB2610.namprd03.prod.outlook.com \
--to=dgowda@rbbn.com \
--cc=dev@dpdk.org \
/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).