From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
dev@dpdk.org, phil.yang@arm.com, thomas@monjalon.net,
arybchenko@solarflare.com, konstantin.ananyev@intel.com,
jerinj@marvell.com, tgw_team@tencent.com
Cc: abhinandan.gujjar@intel.com, nd@arm.com
Subject: Re: [dpdk-dev] [PATCH v2 1/2] lib/ethdev: replace full barrier with relaxed barrier
Date: Wed, 14 Oct 2020 17:36:49 +0100 [thread overview]
Message-ID: <df9ac6cd-bc67-9d82-f5cd-1ea476e649c3@intel.com> (raw)
In-Reply-To: <20201013162537.24029-1-honnappa.nagarahalli@arm.com>
On 10/13/2020 5:25 PM, Honnappa Nagarahalli wrote:
> From: Phil Yang <phil.yang@arm.com>
>
> While registering the call back functions full write barrier
> can be replaced with one-way write barrier.
>
> Signed-off-by: Phil Yang <phil.yang@arm.com>
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-10-14 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 0:07 [dpdk-dev] [PATCH " Honnappa Nagarahalli
2020-10-02 0:07 ` [dpdk-dev] [PATCH 2/2] lib/ethdev: fix memory ordering for call back functions Honnappa Nagarahalli
2020-10-09 2:34 ` Phil Yang
2020-10-13 10:32 ` Ferruh Yigit
2020-10-13 15:25 ` Honnappa Nagarahalli
2020-10-13 14:25 ` Ananyev, Konstantin
2020-10-13 10:30 ` [dpdk-dev] [PATCH 1/2] lib/ethdev: replace full barrier with relaxed barrier Ferruh Yigit
2020-10-13 14:24 ` Ananyev, Konstantin
2020-10-13 16:25 ` [dpdk-dev] [PATCH v2 " Honnappa Nagarahalli
2020-10-13 16:25 ` [dpdk-dev] [PATCH v2 2/2] lib/ethdev: fix memory ordering for call back functions Honnappa Nagarahalli
2020-10-14 16:36 ` 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=df9ac6cd-bc67-9d82-f5cd-1ea476e649c3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=abhinandan.gujjar@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=phil.yang@arm.com \
--cc=tgw_team@tencent.com \
--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).