From: Konstantin Ananyev <konstantin.ananyev@intel.com>
To: dev@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCHv2 0/2] L3FWD sample optimisation
Date: Wed, 11 Jun 2014 14:38:44 +0100 [thread overview]
Message-ID: <1402493926-13401-1-git-send-email-konstantin.ananyev@intel.com> (raw)
v2 changes:
add performance data to the patch comments
fix some checkpatch.pl errors/warnings
Konstantin Ananyev (2):
lpm: Introduce rte_lpm_lookupx4
l3fwd: reorganise and optimize l3fwd LPM code path.
app/test/test_lpm.c | 70 ++++
examples/l3fwd/main.c | 471 ++++++++++++++++++++++--
lib/librte_eal/common/Makefile | 1 +
lib/librte_eal/common/include/rte_common_vect.h | 93 +++++
lib/librte_lpm/rte_lpm.h | 117 ++++++
5 files changed, 728 insertions(+), 24 deletions(-)
create mode 100644 lib/librte_eal/common/include/rte_common_vect.h
--
1.8.3.1
next reply other threads:[~2014-06-11 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 13:38 Konstantin Ananyev [this message]
2014-06-11 13:38 ` [dpdk-dev] [PATCHv2 1/2] lpm: Introduce rte_lpm_lookupx4 Konstantin Ananyev
2014-06-11 13:38 ` [dpdk-dev] [PATCHv2 2/2] l3fwd: reorganise and optimize l3fwd LPM code path Konstantin Ananyev
2014-06-12 10:19 ` [dpdk-dev] [PATCHv2 0/2] L3FWD sample optimisation 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=1402493926-13401-1-git-send-email-konstantin.ananyev@intel.com \
--to=konstantin.ananyev@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).