From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Junchang Wang <junchangwang@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 2/2] Remove unnecessary memory fence
Date: Tue, 9 May 2017 07:47:30 -0700 [thread overview]
Message-ID: <20170509144730.GL3956@linux.vnet.ibm.com> (raw)
In-Reply-To: <1494306511-9022-3-git-send-email-junchangwang@gmail.com>
On Tue, May 09, 2017 at 01:08:31PM +0800, Junchang Wang wrote:
> count_stat_eventual.c uses a single global variable (stopflag) to synchronize
> two separate threads (main and eventual) probably running on two different CPU
> cores. My understanding is that for this model, memory fence instruction
> (mfence) which typically are expensive can be avoided, only if we make sure (1)
> that compiler neither reorder the code around nor cache the variable, and (2)
> that the CPU core running code precedes in program order.
>
> We use keyword ``volatile'' to prevent compilers from reordering the code and
> caching the variable, and instruction barrier() to force CPU core running the
> code to obey program order.
Please take another look at the barrier() macro. It does not emit any
instructions, so cannot force the CPU to do much of anything. Keep in
mind that this code needs to run on weakly ordered systems, not just x86.
Thanx, Paul
> Signed-off-by: Junchang Wang <junchangwang@gmail.com>
> ---
> CodeSamples/count/count_stat_eventual.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/CodeSamples/count/count_stat_eventual.c b/CodeSamples/count/count_stat_eventual.c
> index 059ab8b..5ffc4aa 100644
> --- a/CodeSamples/count/count_stat_eventual.c
> +++ b/CodeSamples/count/count_stat_eventual.c
> @@ -23,7 +23,7 @@
>
> DEFINE_PER_THREAD(unsigned long, counter);
> unsigned long global_count;
> -int stopflag;
> +volatile int stopflag;
>
> void inc_count(void)
> {
> @@ -47,7 +47,7 @@ void *eventual(void *arg)
> ACCESS_ONCE(global_count) = sum;
> poll(NULL, 0, 1);
> if (stopflag) {
> - smp_mb();
> + barrier();
> stopflag++;
> }
> }
> @@ -67,9 +67,9 @@ void count_init(void)
> void count_cleanup(void)
> {
> stopflag = 1;
> + barrier();
> while (stopflag < 3)
> poll(NULL, 0, 1);
> - smp_mb();
> }
>
> #include "counttorture.h"
> --
> 2.7.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2017-05-09 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 5:08 [PATCH 0/2] Reviewing CodeSamples/count/count_stat_eventual.c Junchang Wang
2017-05-09 5:08 ` [PATCH 1/2] Replace definition of variable sum from int to unsigned long Junchang Wang
2017-05-09 14:47 ` Paul E. McKenney
2017-05-09 5:08 ` [PATCH 2/2] Remove unnecessary memory fence Junchang Wang
2017-05-09 14:47 ` Paul E. McKenney [this message]
2017-05-09 15:20 ` Junchang Wang
2017-05-09 15:40 ` Paul E. McKenney
2017-05-09 23:11 ` Junchang Wang
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=20170509144730.GL3956@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=junchangwang@gmail.com \
--cc=perfbook@vger.kernel.org \
/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.