DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] ixgbe: add memory barriers in vector rx/tx
Date: Wed, 21 Oct 2015 17:36:58 +0200	[thread overview]
Message-ID: <1940504.DRviAa2FU5@xps13> (raw)
In-Reply-To: <2020076.2eyxpzhXZx@xps13>

2015-08-03 17:08, Thomas Monjalon:
> 2015-06-29 11:28, Ananyev, Konstantin:
> > There were several discussions about that subject already:
> > why fence is not necessary here for IA and why we don't want to put it here:
> > That I suppose was the last one:
> > http://dpdk.org/ml/archives/dev/2015-April/016463.html
> > As I can see, Dong already submitted patches for  that:
> > http://dpdk.org/dev/patchwork/patch/5884/ 
> > Though I didn't look at it closely yet.
> 
> It will be a good idea to re-open the topic of the cross-arch memory barriers
> at the beginning of the 2.2 cycle.
> Thanks

Any update on this topic?
The patch is still "New" in patchwork.

      reply	other threads:[~2015-10-21 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 18:25 [dpdk-dev] [PATCH 0/2] ixgbe vector rx/tx changes Eric Kinzie
2015-06-25 18:25 ` [dpdk-dev] [PATCH 1/2] ixgbe: vector rx rearm after queue reset Eric Kinzie
2015-08-03 15:07   ` Thomas Monjalon
2015-06-25 18:25 ` [dpdk-dev] [PATCH 2/2] ixgbe: add memory barriers in vector rx/tx Eric Kinzie
2015-06-29 11:28   ` Ananyev, Konstantin
2015-08-03 15:08     ` Thomas Monjalon
2015-10-21 15:36       ` 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=1940504.DRviAa2FU5@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@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).