From: David Marchand <david.marchand@redhat.com>
To: Feifei Wang <feifei.wang2@arm.com>
Cc: dev <dev@dpdk.org>, nd <nd@arm.com>, Ruifeng Wang <ruifeng.wang@arm.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] replace tight loop with wait until equal api
Date: Wed, 20 Oct 2021 08:20:08 +0200 [thread overview]
Message-ID: <CAJFAV8yKLQt_J47va8WQLdyAx8K0XOYbfH-SkS9EZ7r2U6+QOA@mail.gmail.com> (raw)
In-Reply-To: <20211020030335.973360-1-feifei.wang2@arm.com>
On Wed, Oct 20, 2021 at 5:03 AM Feifei Wang <feifei.wang2@arm.com> wrote:
>
> For dpdk/lib, directly use wait_until_equal API to replace tight loop.
>
> v2:
> 1. delete wrong 'volatile' in mcslock (David)
>
> Feifei Wang (2):
> eal/common: use wait until equal API for tight loop
> mcslock: use wait until equal API for tight loop
>
> lib/eal/common/eal_common_mcfg.c | 3 +--
> lib/eal/include/generic/rte_mcslock.h | 3 +--
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
Series applied, thanks.
--
David Marchand
prev parent reply other threads:[~2021-10-20 6:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 8:01 [dpdk-dev] [PATCH v1 " Feifei Wang
2021-08-25 8:01 ` [dpdk-dev] [PATCH v1 1/2] eal/common: use wait until equal API for tight loop Feifei Wang
2021-08-25 8:01 ` [dpdk-dev] [PATCH v1 2/2] mcslock: " Feifei Wang
2021-10-19 11:10 ` David Marchand
2021-10-20 2:46 ` [dpdk-dev] 回复: " Feifei Wang
2021-10-20 2:54 ` Feifei Wang
2021-10-15 10:07 ` [dpdk-dev] 回复: [PATCH v1 0/2] replace tight loop with wait until equal api Feifei Wang
2021-10-20 3:03 ` [dpdk-dev] [PATCH v2 " Feifei Wang
2021-10-20 3:03 ` [dpdk-dev] [PATCH v2 1/2] eal/common: use wait until equal API for tight loop Feifei Wang
2021-10-20 3:03 ` [dpdk-dev] [PATCH v2 2/2] mcslock: " Feifei Wang
2021-10-20 6:20 ` David Marchand [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=CAJFAV8yKLQt_J47va8WQLdyAx8K0XOYbfH-SkS9EZ7r2U6+QOA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=feifei.wang2@arm.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.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).