From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Kulasek, TomaszX" <tomaszx.kulasek@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples: l3fwd exact-match path rework
Date: Wed, 3 Feb 2016 17:58:04 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725836B02E8C@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <1454086113-2228-1-git-send-email-tomaszx.kulasek@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Tomasz Kulasek
> Sent: Friday, January 29, 2016 4:49 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] examples: l3fwd exact-match path rework
>
> Current implementation of Exact-Match uses different execution path than
> for LPM. Unifying them allows to reuse big part of LPM code and sightly
> increase performance of Exact-Match.
>
> Main changes:
> -------------
> * Packet classification stage is separated from the rest of path for both
> LPM and EM.
> * Packet processing, modifying and transmit part is the same for LPM and EM
> and mostly based on the current LPM implementation.
> * Shared code is moved to the common file "l3fwd_sse.h".
> * While sequential packet classification in EM path, seems to be faster
> than using multi hash lookup, used before, it is used by default. Old
> implementation is moved to the file l3fwd_em_hlm_sse.h and can be enabled
> with HASH_LOOKUP_MULTI global define in compilation time.
>
>
> This patch depends of Ravi Kerur's "Modify and modularize l3fwd code" and
> should be applied after it.
>
> Signed-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com>
> ---
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
next prev parent reply other threads:[~2016-02-03 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 16:48 Tomasz Kulasek
2016-02-03 17:58 ` Ananyev, Konstantin [this message]
2016-02-24 9:48 ` [dpdk-dev] [PATCH v2] examples/l3fwd: exact-match rework Tomasz Kulasek
2016-02-28 20:55 ` Thomas Monjalon
2016-02-29 10:33 ` [dpdk-dev] [PATCH v3] " Tomasz Kulasek
2016-02-29 10:45 ` 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=2601191342CEEE43887BDE71AB97725836B02E8C@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=tomaszx.kulasek@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).