From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/4]librte_table: add name parameter to lpm table
Date: Thu, 17 Sep 2015 16:13:29 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126478C846C@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1442505802-10034-1-git-send-email-jasvinder.singh@intel.com>
> -----Original Message-----
> From: Singh, Jasvinder
> Sent: Thursday, September 17, 2015 7:03 PM
> To: dev@dpdk.org
> Cc: Dumitrescu, Cristian
> Subject: [PATCH v2 0/4]librte_table: add name parameter to lpm table
>
> This patchset links to ABI change announced for librte_table. For
> lpm table, name parameter has been included in LPM table parameters
> structure. It will eventually allow applications to create more
> than one instances of lpm table, if required.
>
> Changes in v2:
> - rte_table_lpm_ipv6.c: removed name varibale from
> rte_zmalloc_socket() and inserted that in rte_lpm6_create().
>
>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
next prev parent reply other threads:[~2015-09-17 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 16:03 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 ` [dpdk-dev] [PATCH v2 3/4] ip_pipeline: modify lpm table for routing pipeline Jasvinder Singh
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 ` Dumitrescu, Cristian [this message]
2015-10-12 14:06 ` [dpdk-dev] [PATCH v2 0/4]librte_table: add name parameter to lpm table 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=3EB4FA525960D640B5BDFFD6A3D89126478C846C@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.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).