DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Alex Kiselev <alex@therouter.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] librte_lpm: Improve performance of the delete and add functions
Date: Mon, 9 Jul 2018 10:07:21 +0100	[thread overview]
Message-ID: <20180709090721.GA20456@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <710674507.20180706195922@therouter.net>

On Fri, Jul 06, 2018 at 07:59:22PM +0300, Alex Kiselev wrote:
> Please see inline replies
> 
> > On Mon, Jul 02, 2018 at 07:42:11PM +0300, Alex Kiselev wrote:
> >> There are two major problems with the library:
> >> first, there is no need to rebuild the whole LPM tree
> >> when a rule is deleted and second, due to the current
> >> rules algorithm with complexity O(n) it's almost
> >> impossible to deal with large rule sets (50k or so rules).
> >> This patch addresses those two issues.
> 
> >> Signed-off-by: Alex Kiselev <alex@therouter.net>
> 
> > Hi,
> 
> > Some initial review comments inline below
> 
> > /Bruce
> >> ---
> >>  lib/librte_lpm/rte_lpm6.c | 1073 ++++++++++++++++++++++++++++++++++-----------
> >>  1 file changed, 816 insertions(+), 257 deletions(-)
> 
<snip>
> >> +/*
> >> + * LPM6 rule hash function
> >> + */
> >> +static inline uint32_t
> >> +rule_hash_crc(const void *data, __rte_unused uint32_t data_len,
> >> +               uint32_t init_val)
> >> +{
> >> +     return rte_hash_crc(data, sizeof(struct rte_lpm6_rule_key), init_val);
> >> +}
> 
> > Why bother passing in the length and making the data a void pointer.
>  
> I beleive it should be compatible with the rte_hash_function prototype.

Ah, ok, you are passing this to rte_hash. Makes sense now. I suggest
putting in a comment explaining why you have the extra unused parameter so.

  reply	other threads:[~2018-07-09  9:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c6068a65-bee2-4f34-944a-6cd46ac6a188@orsmsx104.amr.corp.intel.com>
2018-07-06 10:13 ` Bruce Richardson
2018-07-06 10:25   ` Bruce Richardson
2018-07-06 10:23 ` Bruce Richardson
2018-07-06 10:56 ` Bruce Richardson
2018-07-06 12:00   ` Alex Kiselev
2018-07-06 16:16 ` Bruce Richardson
2018-07-06 16:59   ` Alex Kiselev
2018-07-09  9:07     ` Bruce Richardson [this message]
2018-07-09 11:24 ` Bruce Richardson
2018-07-09 12:33   ` Alex Kiselev
2018-07-09 13:35     ` Bruce Richardson
2018-07-02 16:42 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=20180709090721.GA20456@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=alex@therouter.net \
    --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).