From: Atul Shree <Atul.Shree.cs512@cse.iitd.ac.in>
To: dev@dpdk.org
Subject: [dpdk-dev] Why DPDK is not using compressed TRIE for LPM6?
Date: Sat, 27 May 2017 00:34:57 +0530 [thread overview]
Message-ID: <bc76760208b5b2c851e23b116d0a1384@cse.iitd.ac.in> (raw)
Hello All,
I was doing some experiments related to LPM6 look up and I have added
20K
entries in the table. By looking at the rte_lpm6_lookup() code I found
an
opportunity to compress the TRIE and there is a significant improvement
after compression.
Here are my questions:
Q1: Why DPDK is not doing the compression?
Q2. In the worst case the table will behave like an uncompressed TRIE
and
in other cases, there is a scope of improvement. Is it worth doing?
Thank you!
Atul Shree
next reply other threads:[~2017-05-26 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 19:04 Atul Shree [this message]
2017-05-29 9:30 ` Bruce Richardson
2017-05-29 11:54 ` Vladimir Medvedkin
2017-05-29 12:42 ` Dumitrescu, Cristian
2017-05-31 6:10 ` Atul Shree
-- strict thread matches above, loose matches on Subject: below --
2017-05-25 6:32 [dpdk-dev] Why DPDK is not using compressed TRIE for LPM6 ? ankit bhardwaj
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=bc76760208b5b2c851e23b116d0a1384@cse.iitd.ac.in \
--to=atul.shree.cs512@cse.iitd.ac.in \
--cc=cs5120282@cse.iitd.ac.in \
--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).