From: Stephen Hemminger <stephen@networkplumber.org>
To: Alex Kiselev <alex@therouter.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5 1/2] librte_lpm: Improve performance of the delete and add functions
Date: Mon, 16 Jul 2018 08:17:32 -0700 [thread overview]
Message-ID: <20180716081732.05302ae4@xeon-e3> (raw)
In-Reply-To: <5b4c51d3.1c69fb81.7a4de.519aSMTPIN_ADDED_MISSING@mx.google.com>
On Mon, 16 Jul 2018 11:05:27 +0300
Alex Kiselev <alex@therouter.net> wrote:
> librte_lpm: Improve lpm6 performance
>
> Rework the lpm6 rule subsystem and replace
> current rules algorithm complexity O(n)
> with hashtables which allow dealing with
> large (50k) rule sets.
>
> Signed-off-by: Alex Kiselev <alex@therouter.net>
Internet routers can have 1M rule sets.
The cost of a hash table maybe too high then?
next parent reply other threads:[~2018-07-16 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5b4c51d3.1c69fb81.7a4de.519aSMTPIN_ADDED_MISSING@mx.google.com>
2018-07-16 15:17 ` Stephen Hemminger [this message]
2018-07-16 15:36 ` Alex Kiselev
2018-07-16 15:41 ` Alex Kiselev
2018-07-16 8:05 Alex Kiselev
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=20180716081732.05302ae4@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=alex@therouter.net \
--cc=bruce.richardson@intel.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).