From: "Wang, Zhihong" <zhihong.wang@intel.com>
To: "Xu, Qian Q" <qian.q.xu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal: fix rte_memcpy perf in hsw/bdw
Date: Thu, 26 May 2016 09:36:58 +0000 [thread overview]
Message-ID: <8F6C2BD409508844A0EFC19955BE0941107439B6@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E0328B4EE@shsmsx102.ccr.corp.intel.com>
> -----Original Message-----
> From: Xu, Qian Q
> Sent: Thursday, May 26, 2016 1:19 PM
> To: Wang, Zhihong <zhihong.wang@intel.com>; dev@dpdk.org
> Cc: Wang, Zhihong <zhihong.wang@intel.com>
> Subject: RE: [dpdk-dev] [PATCH] eal: fix rte_memcpy perf in hsw/bdw
>
> Tested-by: Qian Xu <qian.q.xu@intel.com>
>
> - Test Commit: 8f6f24342281f59de0df7bd976a32f714d39b9a9
> - OS/Kernel: Fedora 21/4.1.13
> - GCC: gcc (GCC) 4.9.2 20141101 (Red Hat 4.9.2-1)
> - CPU: Intel(R) Xeon(R) CPU E5-2695 v4 @ 2.10
> - Total 1 cases, 1 passed, 0 failed.
[...]
>
> 8. Compare #1 with #2, can see ~5% performance increase on BDW-EP CPU
> server.
Thanks Qian! HSW should suffer even more from this issue.
next prev parent reply other threads:[~2016-05-26 9:37 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 [this message]
2016-06-15 14:21 ` 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=8F6C2BD409508844A0EFC19955BE0941107439B6@SHSMSX103.ccr.corp.intel.com \
--to=zhihong.wang@intel.com \
--cc=dev@dpdk.org \
--cc=qian.q.xu@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).