From: David Marchand <david.marchand@redhat.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev <dev@dpdk.org>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
Gavin Hu <gavin.hu@arm.com>, Phil Yang <phil.yang@arm.com>
Subject: Re: [dpdk-dev] [PATCH] test/mcslock: remove unneeded per-lcore copy
Date: Fri, 15 Jan 2021 16:28:43 +0100 [thread overview]
Message-ID: <CAJFAV8xHhSOKU8Q1bTtuVtrxSSW7P30UmQaWo6ar7i+-Qj9VRg@mail.gmail.com> (raw)
In-Reply-To: <20201104170425.8882-1-olivier.matz@6wind.com>
On Wed, Nov 4, 2020 at 6:05 PM Olivier Matz <olivier.matz@6wind.com> wrote:
>
> Each core already comes with its local storage for mcslock (in its
> stack), therefore there is no need to define an additional per-lcore
> mcslock.
>
> Fixes: 32dcb9fd2a22 ("test/mcslock: add MCS queued lock unit test")
>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2021-01-15 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 17:04 Olivier Matz
2020-11-04 17:57 ` Honnappa Nagarahalli
2020-11-04 21:03 ` Olivier Matz
2020-11-04 21:20 ` Honnappa Nagarahalli
2021-01-15 15:28 ` 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=CAJFAV8xHhSOKU8Q1bTtuVtrxSSW7P30UmQaWo6ar7i+-Qj9VRg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=olivier.matz@6wind.com \
--cc=phil.yang@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).