From: Jasvinder Singh <jasvinder.singh@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 3/4] ip_pipeline: modify lpm table for routing pipeline
Date: Thu, 17 Sep 2015 17:03:21 +0100 [thread overview]
Message-ID: <1442505802-10034-4-git-send-email-jasvinder.singh@intel.com> (raw)
In-Reply-To: <1442505802-10034-1-git-send-email-jasvinder.singh@intel.com>
The name parameter has been defined in lpm table of
routing pipeline.
Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
---
examples/ip_pipeline/pipeline/pipeline_routing_be.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/examples/ip_pipeline/pipeline/pipeline_routing_be.c b/examples/ip_pipeline/pipeline/pipeline_routing_be.c
index 1e817dd..06d3e65 100644
--- a/examples/ip_pipeline/pipeline/pipeline_routing_be.c
+++ b/examples/ip_pipeline/pipeline/pipeline_routing_be.c
@@ -484,6 +484,7 @@ pipeline_routing_init(struct pipeline_params *params,
p->n_tables = 1;
{
struct rte_table_lpm_params table_lpm_params = {
+ .name = p->name,
.n_rules = p_rt->n_routes,
.entry_unique_size = sizeof(struct routing_table_entry),
.offset = p_rt->ip_da_offset,
--
2.1.0
next prev parent reply other threads:[~2015-09-17 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 16:03 [dpdk-dev] [PATCH v2 0/4]librte_table: add name parameter to lpm table Jasvinder Singh
2015-09-17 16:03 ` [dpdk-dev] [PATCH v2 1/4] librte_table: modify LPM table parameter structure Jasvinder Singh
2015-09-17 16:03 ` [dpdk-dev] [PATCH v2 2/4] app/test: modify table and pipeline test Jasvinder Singh
2015-09-17 16:03 ` Jasvinder Singh [this message]
2015-09-17 16:03 ` [dpdk-dev] [PATCH v2 4/4] librte_table: modify release notes and deprecation notice Jasvinder Singh
2015-09-17 16:13 ` [dpdk-dev] [PATCH v2 0/4]librte_table: add name parameter to lpm table Dumitrescu, Cristian
2015-10-12 14:06 ` Thomas Monjalon
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=1442505802-10034-4-git-send-email-jasvinder.singh@intel.com \
--to=jasvinder.singh@intel.com \
--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).