From: Michal Kobylinski <michalx.kobylinski@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] Added a new rte_lpm_config structure for IPv4.
Date: Tue, 8 Mar 2016 21:57:26 +0100 [thread overview]
Message-ID: <1457470648-26415-1-git-send-email-michalx.kobylinski@intel.com> (raw)
A new rte_lpm_config structure is used so LPM library will allocate
exactly the amount of memory which is necessary to hold application’s
rules.
Michal Kobylinski (2):
lpm: added a new rte_lpm_config structure for ipv4
examples: update to use new rte_lpm_config structure for ipv4
app/test/test_func_reentrancy.c | 9 +-
app/test/test_lpm.c | 145 ++++++++++++++++++++----
app/test/test_mp_secondary.c | 7 +-
app/test/test_table_combined.c | 2 +
app/test/test_table_tables.c | 2 +
doc/guides/rel_notes/release_16_04.rst | 5 +
examples/ip_fragmentation/main.c | 7 +-
examples/ip_reassembly/main.c | 7 +-
examples/l3fwd-power/main.c | 10 +-
examples/l3fwd-vf/main.c | 10 +-
examples/l3fwd/l3fwd_lpm.c | 9 +-
examples/load_balancer/init.c | 8 +-
examples/performance-thread/l3fwd-thread/main.c | 8 +-
lib/librte_lpm/rte_lpm.c | 51 ++++++---
lib/librte_lpm/rte_lpm.h | 23 +++-
lib/librte_table/rte_table_lpm.c | 12 +-
lib/librte_table/rte_table_lpm.h | 6 +
17 files changed, 262 insertions(+), 59 deletions(-)
--
1.9.1
next reply other threads:[~2016-03-08 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 20:57 Michal Kobylinski [this message]
2016-03-08 20:57 ` [dpdk-dev] [PATCH 1/2] lpm: added a new rte_lpm_config structure for ipv4 Michal Kobylinski
2016-03-08 20:57 ` [dpdk-dev] [PATCH 2/2] examples: update to use new rte_lpm_config " Michal Kobylinski
2016-03-09 0:47 ` [dpdk-dev] [PATCH 0/2] Added a new rte_lpm_config structure for IPv4 Thomas Monjalon
2016-03-09 12:43 ` [dpdk-dev] [PATCH v2] lpm: added a new rte_lpm_config structure for ipv4 Michal Jastrzebski
2016-03-09 13:16 ` 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=1457470648-26415-1-git-send-email-michalx.kobylinski@intel.com \
--to=michalx.kobylinski@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).