All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ignacio Encinas Rubio <ignacio@iencinas.com>
To: perfbook@vger.kernel.org
Subject: Is Alpha non-other-multicopy atomic?
Date: Fri, 28 Feb 2025 18:31:02 +0100	[thread overview]
Message-ID: <6c2c3199-e092-4909-853e-4fad1ca0f35c@iencinas.com> (raw)

Hello!

I recently looked at memory consistency models with a particular focus on hardware details and
found this book to be great, but I was left wondering about something regarding Alpha's memory 
model. 

I tried to find previous discussions about this but didn't find anything, so I'll go ahead:

Table 15.5: Summary of Memory Ordering states that Alpha is *NOT* Other-Multicopy Atomic but 
I couldn't find the explanation for this. Other sources contradict this statement [1] [2].
[3] Documents ARM's adoption of other-multicopy atomicity, using POWER as an example of 
non-other-multicopy-atomicity but fails to mention Alpha.

Furthermore, [2] models non-other-multicopy-atomicity by having "Read from external" (rfe) not 
impose ordering. Alpha's reference manual [3] Section 5.6.1.5 states 

  If u is a write access Pi:W<m>(x,a) and v is an overlapping read access Pj:R<n>(y,b), u is visible to v only if:
    - u <- v, or
    - u precedes v in processor issue sequence (possible only if Pi=Pj).

Which seems to confirm that Alpha was indeed other-multicopy atomic.

Best regards,
Ignacio


[1] https://arxiv.org/pdf/1707.05923 - First page
[2] http://www0.cs.ucl.ac.uk/staff/j.alglave/these.pdf - Section 4.2.3.1
[3] https://download.majix.org/dec/alpha_arch_ref.pdf


             reply	other threads:[~2025-02-28 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 17:31 Ignacio Encinas Rubio [this message]
2025-02-28 17:34 ` Is Alpha non-other-multicopy atomic? Ignacio Encinas Rubio
2025-03-16 11:37 ` Akira Yokosawa
2025-03-16 17:12   ` Ignacio Encinas Rubio
2025-03-17  9:58     ` Akira Yokosawa
2025-03-18 18:16       ` Ignacio Encinas Rubio

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=6c2c3199-e092-4909-853e-4fad1ca0f35c@iencinas.com \
    --to=ignacio@iencinas.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.