From: Matthew Hall <mhall@mhcomputing.net>
To: Vladimir Medvedkin <medvedkinv@gmail.com>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_lpm with larger nexthops or another method?
Date: Tue, 23 Jun 2015 22:15:13 -0700 [thread overview]
Message-ID: <20150624051513.GA18427@mhcomputing.net> (raw)
In-Reply-To: <20150624042859.GA16171@mhcomputing.net>
OK, I went and made a whole ton of patches to LPM and the tests and examples,
now the selftest errors out... but I think maybe I don't have an adequate
amount of hugepages. How much hugepage memory did people have when they did the selftest successfully before?
I just keep seeing this over and over...
RTE>>lpm_autotest
Error at line 293:
ERROR: LPM Test tests[i]: FAIL
LPM: LPM memory allocation failed
Matthew.
next prev parent reply other threads:[~2015-06-24 5:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 2:29 Matthew Hall
2015-06-22 10:11 ` Vladimir Medvedkin
2015-06-22 17:53 ` Matthew Hall
2015-06-23 3:51 ` Stephen Hemminger
2015-06-23 6:30 ` Matthew Hall
2015-06-23 7:19 ` Vladimir Medvedkin
2015-06-24 4:13 ` Matthew Hall
2015-06-24 4:28 ` Matthew Hall
2015-06-24 5:15 ` Matthew Hall [this message]
2015-06-24 7:04 ` Vladimir Medvedkin
2015-06-24 17:56 ` Matthew Hall
2015-06-26 7:01 ` Matthew Hall
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=20150624051513.GA18427@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=medvedkinv@gmail.com \
/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).