From: "Jastrzebski, MichalX K" <michalx.k.jastrzebski@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Kobylinski, MichalX" <michalx.kobylinski@intel.com>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>,
"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>,
"Glynn, Michael J" <michael.j.glynn@intel.com>
Subject: Re: [dpdk-dev] Patch "Increased number of next hops for LPM IPv4" break IP Pipeline application
Date: Thu, 17 Mar 2016 10:58:04 +0000 [thread overview]
Message-ID: <60ABE07DBB3A454EB7FAD707B4BB158213A3E28C@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <56E6ED4B.9080703@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhang, Roy Fan
> Sent: Monday, March 14, 2016 5:57 PM
> To: dev@dpdk.org; Kobylinski, MichalX <michalx.kobylinski@intel.com>
> Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Singh, Jasvinder
> <jasvinder.singh@intel.com>; thomas.monjalon@6wind.com; Glynn,
> Michael J <michael.j.glynn@intel.com>
> Subject: [dpdk-dev] Patch "Increased number of next hops for LPM IPv4"
> break IP Pipeline application
>
> Hi Michal,
>
> Your patch "Increased number of next hops for LPM IPv4"
> (http://dpdk.org/ml/archives/dev/2016-March/035269.html) is breaking the
> IP Pipeline application. Without this patch, the application runs
> successfully.
>
> The IP Pipeline failed on executing the following command:
> ./build/ip_pipeline -f ./config/edge_router_downstream.cfg -s
> ./config/edge_router_downstream.sh -p 0xf
>
> The error messages:
>
> [PIPELINE1] Routing
> TABLE: rte_table_lpm_create: Invalid number_tbl8s
> PIPELINE: rte_pipeline_table_create: Table creation failed
> PANIC in app_init_pipelines():
> Pipeline instance "PIPELINE1" back-end init error
>
> Regards,
> Fan
Hi all,
A fix for this issue is here:
http://dpdk.org/dev/patchwork/patch/11552/
Michal
prev parent reply other threads:[~2016-03-17 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 16:56 Zhang, Roy Fan
2016-03-17 10:58 ` Jastrzebski, MichalX K [this message]
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=60ABE07DBB3A454EB7FAD707B4BB158213A3E28C@IRSMSX109.ger.corp.intel.com \
--to=michalx.k.jastrzebski@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=michael.j.glynn@intel.com \
--cc=michalx.kobylinski@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=thomas.monjalon@6wind.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).