From: Ferruh Yigit <ferruh.yigit@intel.com>
To: David Marchand <david.marchand@redhat.com>,
Phil Yang <phil.yang@arm.com>
Cc: dev <dev@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"Ruifeng Wang (Arm Technology China)" <Ruifeng.Wang@arm.com>,
Joyce Kong <joyce.kong@arm.com>, nd <nd@arm.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] remove RTE CIO barriers
Date: Thu, 17 Sep 2020 00:22:06 +0100 [thread overview]
Message-ID: <dc61479b-fce0-0850-875c-f28349ae7d49@intel.com> (raw)
In-Reply-To: <CAJFAV8yY_MDJN6WUKWTbmNo=nmd63rMHke0R-jG6qG2p4mJ3Ow@mail.gmail.com>
On 9/16/2020 5:13 PM, David Marchand wrote:
> On Fri, Sep 11, 2020 at 7:26 AM Phil Yang <phil.yang@arm.com> wrote:
>>
>> Since rte_cio_*mb APIs have been deprecated[1], remove them and use
>> rte_io_*mb APIs instead.
>>
>> [1] http://code.dpdk.org/dpdk/latest/source/doc/guides/rel_notes/deprecation.rst#L100
>>
>> v2:
>> Update 20.11 release note by adding these API change announcement. (Honnappa)
>
> Copying Thomas and Ferruh for info, as this change is likely to
> generate some merging noise (I can see new rte_cio_* calls in
> next-net).
>
>
> Phil, you must remove the associated deprecation notice as part of this change.
>
> A single patch is enough since the change is mechanical and the
> rte_io_ barriers are already equivalent.
> Yet, I would remind in the commitlog that this is possible now that
> ARMv8 IO barriers behave the same as the others arches.
>
Thanks for the heads up.
If there will a v3, can it be possible to have it after next-net pulled
to main repo? Which I am hopping one for this week but need to sync with
Thomas. This way no new code is missed.
next prev parent reply other threads:[~2020-09-16 23:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 8:40 [dpdk-dev] [PATCH 1/2] drivers: replace RTE CIO barriers with RTE IO barriers Phil Yang
2020-08-24 8:40 ` [dpdk-dev] [PATCH 2/2] eal: remove RTE CIO barriers Phil Yang
2020-08-24 19:38 ` [dpdk-dev] [PATCH 1/2] drivers: replace RTE CIO barriers with RTE IO barriers Honnappa Nagarahalli
2020-08-25 9:08 ` Phil Yang
2020-09-11 5:26 ` [dpdk-dev] [PATCH v2 0/2] remove RTE CIO barriers Phil Yang
2020-09-11 5:26 ` [dpdk-dev] [PATCH v2 1/2] drivers: replace RTE CIO barriers with RTE IO barriers Phil Yang
2020-09-14 23:00 ` Honnappa Nagarahalli
2020-09-11 5:26 ` [dpdk-dev] [PATCH v2 2/2] eal: remove RTE CIO barriers Phil Yang
2020-09-14 22:51 ` Honnappa Nagarahalli
2020-09-16 16:13 ` [dpdk-dev] [PATCH v2 0/2] " David Marchand
2020-09-16 23:22 ` Ferruh Yigit [this message]
2020-09-17 2:23 ` Phil Yang
2020-09-23 8:35 ` David Marchand
2020-09-23 9:19 ` Phil Yang
2020-09-23 9:16 ` [dpdk-dev] [PATCH v3] " Phil Yang
2020-09-23 9:16 ` [dpdk-dev] [PATCH v3] eal: remove deprecated coherent IO memory barriers Phil Yang
2020-09-23 12:20 ` David Marchand
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=dc61479b-fce0-0850-875c-f28349ae7d49@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=joyce.kong@arm.com \
--cc=nd@arm.com \
--cc=phil.yang@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.