From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Imre Palik <imrep.amz@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: Changing non-volatile access to volatile in counter examples
Date: Mon, 23 Jul 2018 13:55:07 -0700 [thread overview]
Message-ID: <20180723205507.GY12945@linux.vnet.ibm.com> (raw)
In-Reply-To: <1532376448-15103-1-git-send-email-imrep.amz@gmail.com>
On Mon, Jul 23, 2018 at 10:07:24PM +0200, Imre Palik wrote:
>
> This series changes some of the counter examples to use volatile access, to
> avoid overly eager compilers/linkers to optimise out necessary reads/writes.
Applied and pushed, thank you!
And very nice to get that graph upgraded to the much more recent Kaby
Lake! By the way, if you have one with more than eight hardware threads,
I would not say "no" to an expanded graph. ;-)
Thanx, Paul
prev parent reply other threads:[~2018-07-23 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 20:07 Changing non-volatile access to volatile in counter examples Imre Palik
2018-07-23 20:07 ` [PATCH 1/4] Changing counttorture defaults Imre Palik
2018-07-23 20:07 ` [PATCH 2/4] Making the counter implementations safer Imre Palik
2018-07-23 20:07 ` [PATCH 3/4] Updating count.tex with new counter code Imre Palik
2018-07-23 20:07 ` [PATCH 4/4] Regenerating the atomic counter graph on a more modern CPU Imre Palik
2018-07-23 20:55 ` Paul E. McKenney [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=20180723205507.GY12945@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=imrep.amz@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.