From: Noah Goldstein <goldstein.w.n@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Florian Weimer <fweimer@redhat.com>,
Hongyu Wang <hongyu.wang@intel.com>,
Andreas Schwab <schwab@linux-m68k.org>,
liuhongt <hongtao.liu@intel.com>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [PATCH v3] x86: Optimize atomic_compare_and_exchange_[val|bool]_acq [BZ #28537]
Date: Mon, 8 Nov 2021 09:32:16 -0600 [thread overview]
Message-ID: <CAFUsyf+g=aieH9z0vc81=vN8RgJu0CD+0Zs_zWo-9XB6MU6+ww@mail.gmail.com> (raw)
In-Reply-To: <20211104161443.734681-1-hjl.tools@gmail.com>
On Thu, Nov 4, 2021 at 11:15 AM H.J. Lu via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> From the CPU's point of view, getting a cache line for writing is more
> expensive than reading. See Appendix A.2 Spinlock in:
>
> https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/xeon-lock-scaling-analysis-paper.pdf
>
> The full compare and swap will grab the cache line exclusive and cause
> excessive cache line bouncing. Load the current memory value via a
> volatile pointer first, which should be atomic and won't be optimized
> out by compiler, check and return immediately if writing cache line may
> fail to reduce cache line bouncing on contended locks.
>
> This fixes BZ# 28537.
>
> A GCC bug is opened:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103065
>
> The fixed compiler should define __HAVE_SYNC_COMPARE_AND_SWAP_LOAD_CHECK
> to indicate that compiler will generate the check with the volatile load.
> Then glibc can check __HAVE_SYNC_COMPARE_AND_SWAP_LOAD_CHECK to avoid the
> extra volatile load.
> ---
> sysdeps/x86/atomic-machine.h | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/sysdeps/x86/atomic-machine.h b/sysdeps/x86/atomic-machine.h
> index 2692d94a92..597dc1cf92 100644
> --- a/sysdeps/x86/atomic-machine.h
> +++ b/sysdeps/x86/atomic-machine.h
> @@ -73,9 +73,20 @@ typedef uintmax_t uatomic_max_t;
> #define ATOMIC_EXCHANGE_USES_CAS 0
>
> #define atomic_compare_and_exchange_val_acq(mem, newval, oldval) \
> - __sync_val_compare_and_swap (mem, oldval, newval)
> + ({ volatile __typeof (*(mem)) *memp = (mem); \
> + __typeof (*(mem)) oldmem = *memp, ret; \
> + ret = (oldmem == (oldval) \
> + ? __sync_val_compare_and_swap (mem, oldval, newval) \
> + : oldmem); \
> + ret; })
> #define atomic_compare_and_exchange_bool_acq(mem, newval, oldval) \
> - (! __sync_bool_compare_and_swap (mem, oldval, newval))
> + ({ volatile __typeof (*(mem)) *memp = (mem); \
> + __typeof (*(mem)) oldmem = *memp; \
> + int ret; \
> + ret = (oldmem == (oldval) \
> + ? !__sync_bool_compare_and_swap (mem, oldval, newval) \
> + : 1); \
> + ret; })
>
>
> #define __arch_c_compare_and_exchange_val_8_acq(mem, newval, oldval) \
> --
> 2.33.1
>
Worth noting on X86 any of the __atomic_fetch_* builtins aside from add/sub
are implemented with a CAS loop that may benefit from this:
https://godbolt.org/z/z87v9Kbcz
next prev parent reply other threads:[~2021-11-08 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 16:14 H.J. Lu
2021-11-08 15:32 ` Noah Goldstein [this message]
2021-11-08 15:45 ` H.J. Lu
2021-11-08 17:36 ` Florian Weimer
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='CAFUsyf+g=aieH9z0vc81=vN8RgJu0CD+0Zs_zWo-9XB6MU6+ww@mail.gmail.com' \
--to=goldstein.w.n@gmail.com \
--cc=arjan@linux.intel.com \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=hongtao.liu@intel.com \
--cc=hongyu.wang@intel.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).