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: Fri, 6 Jul 2018 11:25:36 +0100 [thread overview]
Message-ID: <20180706102536.GC6220@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20180706101352.GA6220@bricha3-MOBL.ger.corp.intel.com>
On Fri, Jul 06, 2018 at 11:13:53AM +0100, Bruce Richardson wrote:
> 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>
> > ---
> > lib/librte_lpm/rte_lpm6.c | 1073 ++++++++++++++++++++++++++++++++++-----------
> > 1 file changed, 816 insertions(+), 257 deletions(-)
> >
>
> I get a compiler error with gcc8 after this patch:
>
> /home/bruce/dpdk.org/lib/librte_lpm/rte_lpm6.c: In function ‘rte_lpm6_add_v1705’:
> /home/bruce/dpdk.org/lib/librte_lpm/rte_lpm6.c:748:18: error: ‘tbl_next_num’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
> lpm->tbl8_hdrs[tbl_ind].ref_cnt++;
> ^
>
On fixing this, clang errors show up thereafter. I suggest using
"test-meson-builds.sh" to sanity check compile on the patch.
Thanks,
/Bruce
ccache clang -Ilib/lib@@rte_lpm@sta -Ilib -I../lib -Ilib/librte_lpm -I../lib/librte_lpm -I. -I../ -Iconfig -I../config -Ilib/librte_eal/common -I../lib/librte_eal/common -Ilib/librte_eal/common/include -I../lib/librte_eal/common/include -Ilib/librte_eal/common/include/arch/x86 -I../lib/librte_eal/common/include/arch/x86 -I../lib/librte_eal/linuxapp/eal/include -Ilib/librte_eal/linuxapp/eal/../../../librte_compat -I../lib/librte_eal/linuxapp/eal/../../../librte_compat -Ilib/librte_eal -I../lib/librte_eal -Ilib/librte_compat -I../lib/librte_compat -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring -I../lib/librte_ring -Ilib/librte_hash -I../lib/librte_hash -Xclang -fcolor-diagnostics -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O3 -include rte_config.h -Wsign-compare -Wcast-qual -Wno-address-of-packed-member -fPIC -march=native -MD -MQ 'lib/lib@@rte_lpm@sta/librte_lpm_rte_lpm6.c.o' -MF 'lib/lib@@rte_lpm@sta/librte_lpm_rte_lpm6.c.o.d' -o 'lib/lib@@rte_lpm@sta/librte_lpm_rte_lpm6.c.o' -c ../lib/librte_lpm/rte_lpm6.c
../lib/librte_lpm/rte_lpm6.c:233:58: error: cast from 'struct rte_lpm6_rule **' to 'const void **' must have all intermediate pointers const qualified to be safe [-Werror,-Wcast-qual]
while (rte_hash_iterate(lpm->rules_tbl, (const void **) &rule_key,
^
../lib/librte_lpm/rte_lpm6.c:247:58: error: cast from 'struct rte_lpm6_rule **' to 'const void **' must have all intermediate pointers const qualified to be safe [-Werror,-Wcast-qual]
while (rte_hash_iterate(lpm->rules_tbl, (const void **) &rule_key,
^
next prev parent reply other threads:[~2018-07-06 10:25 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 [this message]
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
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=20180706102536.GC6220@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).