From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Zhihong Wang <zhihong.wang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: fix rte_memcpy perf in hsw/bdw
Date: Wed, 15 Jun 2016 16:21:08 +0200 [thread overview]
Message-ID: <9020918.HyCU59pmu8@xps13> (raw)
In-Reply-To: <1464139383-132732-1-git-send-email-zhihong.wang@intel.com>
2016-05-24 21:23, Zhihong Wang:
> This patch fixes rte_memcpy performance in Haswell and Broadwell for
> vhost when copy size larger than 256 bytes.
>
> It is observed that for large copies like 1024/1518 ones, rte_memcpy
> suffers high ratio of store buffer full issue which causes pipeline
> to stall in scenarios like vhost enqueue. This can be alleviated by
> adjusting instruction layout. Note that this issue may not be visible
> in micro test.
>
> How to reproduce?
>
> PHY-VM-PHY using vhost/virtio or vhost/virtio loop back, with large
> packets like 1024/1518 bytes ones. Make sure packet generation rate
> is not the bottleneck if PHY-VM-PHY is used.
>
> Signed-off-by: Zhihong Wang <zhihong.wang@intel.com>
Test report: http://dpdk.org/ml/archives/dev/2016-May/039716.html
Applied, thanks
prev parent reply other threads:[~2016-06-15 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 1:23 Zhihong Wang
2016-05-26 5:19 ` Xu, Qian Q
2016-05-26 9:36 ` Wang, Zhihong
2016-06-15 14: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=9020918.HyCU59pmu8@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=zhihong.wang@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).