From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Feifei Wang <Feifei.Wang2@arm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>,
Ruifeng Wang <Ruifeng.Wang@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v1 1/2] app/test: remove unnecessary barriers for ring stress test
Date: Wed, 27 Jan 2021 23:00:40 +0000 [thread overview]
Message-ID: <DBAPR08MB58147DDADE8F32829D8026ED98BB0@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <BYAPR11MB3301F5D4B687E2E66AE6CCEC9ADF0@BYAPR11MB3301.namprd11.prod.outlook.com>
<snip>
>
> Hi Feifei,
>
> >
> > The variable "wrk_cmd" is a signal to control threads from running and
> > stopping. When worker lcores load "wrk_cmd == WRK_CMD_RUN", they
> start
> > running and when worker lcores load "wrk_cmd == WRK_CMD_STOP",
> they
> > stop.
> >
> > For the wmb in test_mt1, no storing operations must keep the order
> > after storing "wrk_cmd". Thus the wmb is unnecessary.
>
> I think there is a bug in my original code, we should do smp_wmb() *before*
> setting wrk_cmd, not after:
>
> /* launch on all workers */
> RTE_LCORE_FOREACH_WORKER(lc) {
> arg[lc].rng = r;
> arg[lc].stats = init_stat;
> rte_eal_remote_launch(test, &arg[lc], lc);
> }
>
> /* signal worker to start test */
> + rte_smp_wmb();
> wrk_cmd = WRK_CMD_RUN;
> - rte_smp_wmb();
>
> usleep(run_time * US_PER_S);
>
>
> I still think we'd better have some synchronisation here.
> Otherwise what would prevent compiler and/or cpu to update wrk_cmd out
> of order (before _init_ phase is completed)?
> We probably can safely assume no reordering from the compiler here, as we
> have function calls straight before and after 'wrk_cmd = WRK_CMD_RUN;'
> But for consistency and easier maintenance, I still think it is better to have
> something here, after all it is not performance critical pass.
Agree that this is not performance critical.
This is more about correctness (as usually people refer to code to understand the concepts). You can refer to video [1]. Essentially, the pthread_create has 'happens-before' behavior. i.e. all the memory operations before the pthread_create are visible to the new thread. The rte_smp_rmb() barrier in the thread function is not required as it reads the data that was set before the thread was launched.
I do not know why rte_smp_wmb is required. The update to 'wrk_cmd' is seen by the thread eventually. rte_smp_wmb does not result in update being seen sooner/immediately.
[1] https://www.youtube.com/watch?t=4170&v=KeLBd2EJLOU&feature=youtu.be
>
> > For the rmb in test_worker, the parameters have been prepared when
> > worker lcores call "test_worker". It is unnessary to wait wrk_cmd to
> > be loaded, then the parameters can be loaded, So the rmb can be
> removed.
>
> It is not only about parameters loading, it is to prevent worker core to start
> too early.
Because 'pthread_launch' provides the 'happens-before' behavior, the worker core will see the updates that happened before the worker was launched.
I suggest changing the commit log to provide the reasoning around pthread_create.
>
> As I understand, your goal is to get rid of rte_smp_*() calls.
> Might be better to replace such places here with _atomic_ semantics.
> Then, as I can see, we also can get rid of 'volatile' fo wrk_cmd.
>
> > In the meanwhile, fix a typo. The note above storing "stop" into
> > "wrk_cmd" should be "stop test" rather than "start test".
> >
> > Signed-off-by: Feifei Wang <feifei.wang2@arm.com>
> > Reviewed-by: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
> > Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
> > ---
> > app/test/test_ring_stress_impl.h | 5 +----
> > 1 file changed, 1 insertion(+), 4 deletions(-)
> >
> > diff --git a/app/test/test_ring_stress_impl.h
> > b/app/test/test_ring_stress_impl.h
> > index f9ca63b90..384555ef9 100644
> > --- a/app/test/test_ring_stress_impl.h
> > +++ b/app/test/test_ring_stress_impl.h
> > @@ -198,7 +198,6 @@ test_worker(void *arg, const char *fname, int32_t
> prcs)
> > fill_ring_elm(&loc_elm, lc);
> >
> > while (wrk_cmd != WRK_CMD_RUN) {
> > - rte_smp_rmb();
> > rte_pause();
> > }
> >
> > @@ -357,13 +356,11 @@ test_mt1(int (*test)(void *))
> >
> > /* signal worker to start test */
> > wrk_cmd = WRK_CMD_RUN;
> > - rte_smp_wmb();
> >
> > usleep(run_time * US_PER_S);
> >
> > - /* signal worker to start test */
> > + /* signal worker to stop test */
> > wrk_cmd = WRK_CMD_STOP;
> > - rte_smp_wmb();
> >
> > /* wait for workers and collect stats. */
> > mc = rte_lcore_id();
> > --
> > 2.17.1
next prev parent reply other threads:[~2021-01-27 23:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 6:30 [dpdk-dev] [PATCH v1 0/2] remove smp barriers in app/test Feifei Wang
2020-12-22 6:30 ` [dpdk-dev] [PATCH v1 1/2] app/test: remove unnecessary barriers for ring stress test Feifei Wang
2020-12-22 12:42 ` Ananyev, Konstantin
2021-01-27 23:00 ` Honnappa Nagarahalli [this message]
2021-01-28 14:43 ` Ananyev, Konstantin
2021-01-29 3:17 ` Honnappa Nagarahalli
2021-01-29 4:58 ` Stephen Hemminger
2021-01-30 1:24 ` Honnappa Nagarahalli
2021-02-01 8:37 ` [dpdk-dev] 回复: " Feifei Wang
2021-02-01 13:50 ` [dpdk-dev] " Ananyev, Konstantin
2021-02-03 16:24 ` Honnappa Nagarahalli
2021-02-01 8:48 ` [dpdk-dev] 回复: " Feifei Wang
2021-02-01 9:07 ` Feifei Wang
2020-12-22 6:30 ` [dpdk-dev] [PATCH v1 2/2] app/test: collect perf data after worker threads exit Feifei Wang
2021-03-10 2:12 ` [dpdk-dev] [PATCH v3 0/1] remove smp barriers in app/test Feifei Wang
2021-03-10 2:12 ` [dpdk-dev] [PATCH v3 1/1] test/trace: collect perf data after worker threads exit Feifei Wang
2021-03-10 2:15 ` [dpdk-dev] [PATCH v3 0/1] remove smp barriers in app/test Feifei Wang
2021-03-10 2:15 ` [dpdk-dev] [PATCH v3 1/1] test/trace: collect perf data after worker threads exit Feifei Wang
2021-04-14 14:14 ` 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=DBAPR08MB58147DDADE8F32829D8026ED98BB0@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=Feifei.Wang2@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=nd@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).