DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jianbo Liu <jianbo.liu@linaro.org>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "Yao, Lei A" <lei.a.yao@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
	 "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:36:37 +0800	[thread overview]
Message-ID: <CAP4Qi3-5V-7hmd4EFdYardsFa8WVwBk_+DgtzzoH0s2RGPMJpw@mail.gmail.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB97725836B8D25C@irsmsx105.ger.corp.intel.com>

On 3 August 2016 at 16:29, Ananyev, Konstantin
<konstantin.ananyev@intel.com> wrote:
>
> Hi Jianbo,
>
>> > Hi, Jianbo
>> >
>> > I have tested you patch on my X86 platform,  the single core performance for Non-vector PMD will have about 1Mpps drop
>> > Non-vector PMD single core performance with patch               :  ~33.9 Mpps
>> > Non-vector PMD single core performance without patch        :  ~35.1 Mpps
>> > Is there any way to avoid such performance drop on X86? Thanks.
>> >
>>
>> 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)
>
> I suppose you can use rte_smp_rmb() here?

Great. Thank Konstantin.
I'll send v2.

Jianbo

  reply	other threads:[~2016-08-03  9:36 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
2016-08-03  8:29       ` Ananyev, Konstantin
2016-08-03  9:36         ` Jianbo Liu [this message]
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-5V-7hmd4EFdYardsFa8WVwBk_+DgtzzoH0s2RGPMJpw@mail.gmail.com \
    --to=jianbo.liu@linaro.org \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=lei.a.yao@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).