3 ms·
There you go.[0] I believe it's called the 'arbiter problem' in that context, and your description seems basically correct. [0]: http://research.microsoft.com/
by bkirwi 12y ago
There you go.[0] I believe it's called the 'arbiter problem' in that context, and your description seems basically correct.
[0]: http://research.microsoft.com/en-us/um/people/lamport/pubs/buridan.pdf http://research.microsoft.com/en-us/um/people/lamport/pubs/b...
- schoen 12y agoWhoa, that paper is fascinating! I'm trying to improve my intuition for why the physical exmaples in it are right. I found the examples of inevitable crashes and collisions disconcerting.
- Animats 12y agoYes. This is a well known problem. See (https://en.wikipedia.org/wiki/Arbiter_[electronics] https://en.wikipedia.org/wiki/Arbiter_[electronics]). It's not possible to build an arbiter which will reliably decide who wins in a fixed time. It is, however, possible to design one which can detect that the arbiter hasn't stabilized yet and delays until it has. All multiprocessor shared-memory systems need this.