From d9dabf4653255641634523e1e25e9e614e0f7b09 Mon Sep 17 00:00:00 2001 From: SabrinaJewson Date: Sun, 4 Sep 2022 18:23:56 +0100 Subject: [PATCH] Note that a release fence followed by multiple stores is not necessarily faster than many release stores --- src/atomics/fences.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/src/atomics/fences.md b/src/atomics/fences.md index 9de55d1..210234b 100644 --- a/src/atomics/fences.md +++ b/src/atomics/fences.md @@ -170,10 +170,11 @@ The execution with the relation looks like this: ╰───────╯ └───┴──┘╰───────╯ ``` -Like with acquire fences, release fences are commonly used to optimize over a -series of atomic stores that don’t individually need to be `Release`, since it’s -often faster to put a single release fence at the start and use `Relaxed` from -that point on than it is to use `Release` every time. +Like with acquire fences, release fences can be used to optimize over a series +of atomic stores that don’t individually need to be `Release`, since in some +conditions and on some architectures it’s faster to put a single release fence +at the start and use `Relaxed` from that point on than it is to use `Release` +every time. ## `AcqRel` fences