From: Thomas Monjalon <thomas@monjalon.net>
To: Feifei Wang <feifei.wang@arm.com>
Cc: dev@dpdk.org, gavin.hu@arm.com, ruifeng.wang@arm.com,
phil.yang@arm.com, Honnappa.Nagarahalli@arm.com, nd@arm.com,
konstantin.ananyev@intel.com
Subject: Re: [dpdk-dev] [PATCH] examples/l3fwd: prefetch the content of the next packet
Date: Sun, 27 Oct 2019 18:21:28 +0100 [thread overview]
Message-ID: <1973460.tJ4aIHWnQC@xps> (raw)
In-Reply-To: <1565772870-24903-1-git-send-email-feifei.wang@arm.com>
+Cc Konstantin
14/08/2019 10:54, Feifei Wang:
> The cache-misses problem is very serious when the function
> lpm_cb_parse_ptype is called to read the content of packets. That is
> because the contents of packages previously stored in the cache are
> overwritten by the following instructions or variables.
> Thus the prefetch order can be used to prefetch the next packet into
> the cache to avoid CPU spending too much time on it.
>
> On Octeon TX platform with built-in NIC, 12% performance gain was
> measured by running RFC2544 NDR test with l3fwd. Furthermore, the
> cache-misses event of the function lpm_cb_parse_ptype was reduced by
> 20%, and the CPU task-clock of it dropped from 16.49% to 11.3%, based
> on the forwarding test for one minute with the 64B packet.
> On the dpaa2 platform, no performance improvement nor drop were seen
> with this patch by running RFC2544 NDR test with l3fwd.
> On the x86 platform, 15.7% performance gain was measured by running
> RFC2544 NDR test with l3fwd.
>
> Signed-off-by: Feifei Wang <feifei.wang@arm.com>
> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Reviewed-by: Phil Yang <phil.yang@arm.com>
Let's test this "improvement" with 19.11-rc1.
If a drawback is seen, the patch can be reverted.
Applied, thanks
prev parent reply other threads:[~2019-10-27 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 8:54 Feifei Wang
2019-10-27 17:21 ` 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=1973460.tJ4aIHWnQC@xps \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=feifei.wang@arm.com \
--cc=gavin.hu@arm.com \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=phil.yang@arm.com \
--cc=ruifeng.wang@arm.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).