From: Jianbo Liu <jianbo.liu@linaro.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, "Yao, Lei A" <lei.a.yao@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] i40e: enable i40e pmd on ARM platform
Date: Wed, 3 Aug 2016 17:33:03 +0800 [thread overview]
Message-ID: <CAP4Qi3-y3vJh7Z6jpwOEevZ=H0qxERf6Jo6bjnSWs2z1agbJHA@mail.gmail.com> (raw)
In-Reply-To: <3008268.1MMmpoWvzz@xps13>
Hi Thomas,
On 3 August 2016 at 15:58, Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> 2016-08-03 14:02, Jianbo Liu:
>> I think we can place a compiling condition before rte_rmb() to avoid
>> performance decrease on x86.
>> For example: #if defined(RTE_ARCH_ARM) || defined(RTE_ARCH_ARM64)
>
> Please could you explain why a memory barrier would be needed on ARM but
The reason is that ARM is weealy ordered processor, and data access
will be executed out of order to improve performance.
In this case, we have to read 2 times, 8 descriptors each. The read
statuses could be wrong if no memory barrier.
I also got the outdated status for some descriptors in my testing.
> not on x86? What about other architectures?
I think Konstantin gave me a good solution, by using rte_smp_rmb :)
Jianbo
next prev parent reply other threads:[~2016-08-03 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 6:58 Jianbo Liu
[not found] ` <82F45D86ADE5454A95A89742C8D1410E0330A4B6@shsmsx102.ccr.corp.intel.com>
2016-08-03 3:26 ` Yao, Lei A
2016-08-03 6:02 ` Jianbo Liu
2016-08-03 7:58 ` Thomas Monjalon
2016-08-03 9:33 ` Jianbo Liu [this message]
2016-08-03 8:29 ` Ananyev, Konstantin
2016-08-03 9:36 ` Jianbo Liu
2016-08-03 10:12 ` [dpdk-dev] [PATCH v2] " Jianbo Liu
2016-08-05 9:06 ` [dpdk-dev] [PATCH v3] " Jianbo Liu
2016-09-23 1:13 ` Zhang, Qi Z
2016-09-27 13:39 ` Bruce Richardson
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='CAP4Qi3-y3vJh7Z6jpwOEevZ=H0qxERf6Jo6bjnSWs2z1agbJHA@mail.gmail.com' \
--to=jianbo.liu@linaro.org \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jingjing.wu@intel.com \
--cc=lei.a.yao@intel.com \
--cc=thomas.monjalon@6wind.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).