Jump to content

Talk:Consistency model

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Blaisorblade (talk | contribs) at 05:31, 26 December 2008 (→Confusion: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

I notice that the external link to lecture notes suggest that they are copyright Ian Welch 2004. However, the slides bear a striking resemblance to Andrew Tanenbaum's slides that accompany Chapter 6 of his Distributed Systems book[1]. I'm not sure of the policy regarding this. Any thoughts? Tim Watson 18:18, 24 January 2006 (UTC)[reply]

What are these "rules" that a programmer must follow to maintain consistency? —Preceding unsigned comment added by 128.138.64.20 (talk) 05:45, 27 February 2008 (UTC)[reply]

Confusion

The article says "To hold the contract, compilers may reorder some memory instructions". It is widely known that the reverse is true: the compiler may reorder instructions to optimize the code, but in some cases to ensure consistency this must be prevented (by usage of locking constructs or optimization barriers). I'm not sure if the author meant something else, or if this is plain confusion. --Blaisorblade (talk) 05:31, 26 December 2008 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:Consistency_model&oldid=260134753"