DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alex Kiselev <alex@therouter.net>
To: Stephen Hemminger <stephen@networkplumber.org>
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 18:41:21 +0300	[thread overview]
Message-ID: <154967581.20180716184121@therouter.net> (raw)
In-Reply-To: <192110016.20180716183625@therouter.net>

Здравствуйте, Alex.

Вы писали 16 июля 2018 г., 18:36:25:


>> 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?
> If I am not mistaken cuckoo hash algorithm on which the rte_hash is 
> based is just a plain array logically divided into buckets.

> So, I am not introducing any memory overhead in comparison
> with current rule storage implementation that uses a plain array.

Strictly speaking I do, since I use a multiplier 1.2 when calculating
hash size based on the given number of rules. So, overhead is 20%.

-- 
Alex

  reply	other threads:[~2018-07-16 15:41 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
2018-07-16 15:36   ` Alex Kiselev
2018-07-16 15:41     ` Alex Kiselev [this message]
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=154967581.20180716184121@therouter.net \
    --to=alex@therouter.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).