From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>, dev@dpdk.org
Cc: stable@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/nfp: fix barrier location
Date: Wed, 7 Mar 2018 11:51:13 +0000 [thread overview]
Message-ID: <08903494-e046-9282-9557-0ec733298c87@intel.com> (raw)
In-Reply-To: <1519299039-2475-1-git-send-email-alejandro.lucero@netronome.com>
On 2/22/2018 11:30 AM, Alejandro Lucero wrote:
> The barrier needs to be after reading the DD bit. It has not been
> a problem because the potential reads which can not happen before
> reading the DD bit seem to be far enough, so the compiler is not
> rescheduling them. However, a refactoring could make this problem
> to arise.
>
> Fixes: b812daadad0d ("nfp: add Rx and Tx")
Cc: stable@dpdk.org
>
> Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
Applied to dpdk-next-net/master, thanks.
Unrelated to this patch but nfp driver is still missing:
1- SPDX licensing tags
2- new offloading API.
Can you please plan for them for this release? Specially second one is important
because missing it may break the driver for this release.
Thanks,
ferruh
prev parent reply other threads:[~2018-03-07 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 11:30 [dpdk-dev] " Alejandro Lucero
2018-03-07 11:51 ` Ferruh Yigit [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=08903494-e046-9282-9557-0ec733298c87@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).