public inbox for perfbook@vger.kernel.org
 help / color / mirror / Atom feed
From: Kunwu Chan <kunwu.chan@linux.dev>
To: perfbook@vger.kernel.org
Cc: paulmck@kernel.org, Kunwu Chan <kunwu.chan@linux.dev>
Subject: [PATCH] memorder: Reconcile W+RWC propagation path with litmus dataflow
Date: Wed, 11 Mar 2026 15:58:06 +0800	[thread overview]
Message-ID: <20260311075806.950363-1-kunwu.chan@linux.dev> (raw)

Align the Section 15.3.7.2 propagation narrative with Listing 15.18 by correcting the path to P2->z->P1. This removes a variable-path contradiction in the counter-temporal explanation and restores argument traceability.

Signed-off-by: Kunwu Chan <kunwu.chan@linux.dev>
---
 memorder/memorder.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/memorder/memorder.tex b/memorder/memorder.tex
index 16a569d1..2357e7ea 100644
--- a/memorder/memorder.tex
+++ b/memorder/memorder.tex
@@ -2755,8 +2755,8 @@ This situation might seem completely counter-intuitive, but keep
 in mind that the speed of light is finite and computers are of
 non-zero size.
 It therefore takes time for the effect of the \co{P2()}'s store to
-\co{x} to propagate to \co{P1()}, which in turn means that it is possible
-that \co{P1()}'s read from \co{x} happens much later in time, but
+\co{z} to propagate to \co{P1()}, which in turn means that it is possible
+that \co{P1()}'s read from \co{z} happens much later in time, but
 nevertheless still sees the old value of zero.
 This situation is depicted in
 \cref{fig:memorder:Load-to-Store is Counter-Temporal}:
-- 
2.25.1


                 reply	other threads:[~2026-03-11  7:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260311075806.950363-1-kunwu.chan@linux.dev \
    --to=kunwu.chan@linux.dev \
    --cc=paulmck@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox