dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: "Dong.Wang" <dong.wang.pro-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: [PATCH] ixgbe:Add write memory barrier for recv pkts.
Date: Wed, 15 Apr 2015 09:06:42 -0700	[thread overview]
Message-ID: <20150415090642.0137f4c9@urahara> (raw)
In-Reply-To: <BLU436-SMTP22AEE6E7C0129FF42E71B2BFE50-MsuGFMq8XAE@public.gmane.org>

On Wed, 15 Apr 2015 21:46:27 +0800
Dong.Wang <dong.wang.pro-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org> wrote:

> Yes, current implementation works well with IA, and the transmit packets 
> function's rte_wmb() is also unneccessary.
> 
> But there are two reasons for adding rte_wmb() in recv pkts function:
> 1) The memory barrier in recv pkts function and xmit pkts function are 
> inconsistent, rte_wmb() should be added to recv pkts function or be 
> removed from xmit pkts function.
> 2) DPDK will support PowerPC processor (Other developers are working on 
> it), I check the memory ordering of PowerPC, there was no mention of 
> store-store instruction's principle in MPC8544 Reference Manual, only 
> said it is weak memory ordering.
> 
> So, I think it is neccessary to add rte_wmb() to recv pkts function.
> 
> Dong

If PowerPC requires additional memory barriers then it should
introduce a new generic set of memory barrier macros that are no-ops
on other architectures.

Please don't penalize x86 for places where other CPU's have
weaker consistency.

  parent reply	other threads:[~2015-04-15 16:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11 15:33 [PATCH] ixgbe:Add write memory barrier for recv pkts WangDong
     [not found] ` <BLU436-SMTP1791A6BD70260D97089EDBFBFF90-MsuGFMq8XAE@public.gmane.org>
2015-04-14 22:50   ` Ananyev, Konstantin
     [not found]     ` <2601191342CEEE43887BDE71AB97725821415A3A-pww93C2UFcwu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-04-15 13:46       ` Dong.Wang
     [not found]         ` <BLU436-SMTP22AEE6E7C0129FF42E71B2BFE50-MsuGFMq8XAE@public.gmane.org>
2015-04-15 16:06           ` Stephen Hemminger [this message]
2015-04-16 11:29             ` Wang Dong
2015-04-15 22:52           ` Ananyev, Konstantin
     [not found]             ` <2601191342CEEE43887BDE71AB97725821415E37-pww93C2UFcwu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-04-16 11:36               ` Wang Dong
     [not found]                 ` <BLU436-SMTP198103C46C2C7C9EBA5C96ABFE40-MsuGFMq8XAE@public.gmane.org>
2015-04-16 15:14                   ` Ananyev, Konstantin
     [not found]                     ` <2601191342CEEE43887BDE71AB9772582141626B-pww93C2UFcwu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-04-16 15:55                       ` David Marchand
2015-05-05 15:52                       ` Dong Wang
  -- strict thread matches above, loose matches on Subject: below --
2015-04-16 15:55 Dong Wang
2015-04-16 15:58 Dong Wang

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=20150415090642.0137f4c9@urahara \
    --to=stephen-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=dong.wang.pro-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org \
    /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).