From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] l3fwd improve grouping by destination port a bit
Date: Fri, 01 Aug 2014 18:27:22 +0200 [thread overview]
Message-ID: <1663592.FtpoT9rkYr@xps13> (raw)
In-Reply-To: <1406045087-9625-1-git-send-email-konstantin.ananyev@intel.com>
2014-07-22 17:04, Konstantin Ananyev:
> Latest changes introduced a small degradation for the corner case
> when each input packet is destined to the different port.
> For the test-case when 1 core manages 4 ports and packet stream looks like:
> IPV4_DSTPORT0, IPV4_DSTPORT1, IPV4_DSTPORT3, IPV4_DSTPORT4, IPV4_DSTPORT0, ...
> non-optimised code path outperforms optimised one by 2-3%.
> These changes supposed to close that gap.
> From my testing: now for the case descirbed above optimised code path
> produces same numbers as non-optimised one.
> For other test-cases numbers remain about the same.
>
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
There was no comment about this patch so it's now applied for version 1.7.1.
Thanks
--
Thomas
prev parent reply other threads:[~2014-08-01 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 16:04 Konstantin Ananyev
2014-08-01 16:27 ` Thomas Monjalon [this message]
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=1663592.FtpoT9rkYr@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@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).