Content deleted Content added
style: def. articles removed |
Citation bot (talk | contribs) Alter: url, template type, title. URLs might have been internationalized/anonymized. Add: isbn. Correct ISBN10 to ISBN13. | You can use this bot yourself. Report bugs here. | Suggested by AManWithNoPlan | All pages linked from cached copy of User:AManWithNoPlan/sandbox2 | via #UCB_webform_linked 349/6325 |
||
Line 2:
{{More references|date=September 2014}}
'''Lockstep''' systems are [[fault-tolerant computer system]]s that run the same set of operations at the same time in [[Parallel computing|parallel]].<ref>{{cite
| url = https://books.google.com/books?id=UVlq7SFDCVUC&
| title = Fault-Tolerant Real-Time Systems: The Problem of Replica Determinism
| year = 1996 | accessdate = 2014-09-08
| author = Stefan Poledna | website = books.google.com
| page = 80
| isbn = 9780585295800
}}</ref> The [[Redundancy (engineering)|redundancy]] (duplication) allows error detection and error correction: the output from lockstep operations can be compared to determine if there has been a fault if there are at least two systems ([[dual modular redundancy]]), and the error can be automatically corrected if there are at least three systems ([[triple modular redundancy]]), via majority vote. The term "[[lockstep]]" originates from army usage, where it refers to synchronized walking, in which marchers walk as closely together as physically practical.
To run in lockstep, each system is set up to progress from one well-defined state to the next well-defined state. When a new set of inputs reaches the system, it processes them, generates new outputs and updates its state. This set of changes (new inputs, new outputs, new state) is considered to define that step, and must be treated as an atomic transaction; in other words, either all of it happens, or none of it happens, but not something in between. Sometimes a timeshift (delay) is set between systems, which increases the detection probability of errors induced by external influences (e.g. [[voltage spike]]s, [[ionizing radiation]], or [[in situ]] [[reverse engineering]]).
Line 22 ⟶ 23:
}}</ref><ref name="intel-lockstep-mode">{{cite web
| url = https://software.intel.com/en-us/blogs/2014/07/11/independent-channel-vs-lockstep-mode-drive-you-memory-faster-or-safer
| title = Independent Channel vs. Lockstep Mode –
| date = 2014-07-11 | accessdate = 2014-09-09
| author = Thomas Willhalm | publisher = [[Intel]]
| |||