4 ms·
"synchronize" literally has the word "time" in it as a greek root (χρόνο/chrónos). Time is fine for synchronizing when all components are actually reading and
by kazinator 3y ago
"synchronize" literally has the word "time" in it as a greek root (χρόνο/chrónos).
Time is fine for synchronizing when all components are actually reading and acting in accordance with a clock, and agree on using the same one (or a well-characterized facsimile of the same one).
Time is used at the bottom layers of hardware. Certain components generate a signal, and expect the response signal to be settled within a certain time.
Even in situations in which there is robust signaling (like a device can indicate for indefinite periods that it is "not ready" and another device will wait), the underlying signals on which that is based have to meet timing constraints.
You have rules like "when pin X is driven high, the data is expected to be present on lines Y_0 through Y_32 within time T_x." If not, there will be garbage.
All notion order in the machine rests on arbitrary timing at the lowest electronic design level.
- marcosdumay 3y ago> "synchronize" literally has the word "time" in it as a greek root (χρόνο/chrónos). Oh, yeah, the simple times before everybody learned that time is a local and observer-dependent measure. Modern computers do almost none time-based at-distance synchronization. About 2 decades ago, when I was studying asynchronous computation, hacking the chip-design process to make it possible to do time-based synchronization of nearby transistors on the same silicon crystal was a very trendy idea. It was very hard, because everything is extremely noisy, and I imagine the idea faded away, because everything is much more noisy nowadays. Doing that on any large scale is asking for everything to break. For all of the computer-era, synchronization has being done by signaling. The millenia-old tech of doing it by time is just deprecated.
- kazinator 3y agoHow does signaling work without time?
- marcosdumay 3y agoI'm having a really hard time understanding your question. If it's on the line of "signals only exist because we have time", then yeah, duh; and it's such an outrageous misconstruction of my comment that I imagine you meant something else.
- Brian_K_White 3y agoI don't think they understand their question either.
- distcs 3y agoThe question "How does signaling work without time?" makes complete sense to me. I understand this question. Do you not? The question is actually a rhetoric implying that "signalling" in the chip level involves time, namely, the clock signal that is firing periodically. It is not so much as a signalling as it is like an assumption baked into the circuit design. The circuit must change its state from one state to another only at the next clock signal and not before that.
- Brian_K_White 3y agoWell there you go. Physical events are not in fact limited to occurring at clock transitions. But even if they did, it still doesn't make any particular amount of time into a correct stand-in for a serial dependency. The passage of 150ms of time is not what makes thing B clear to proceed. The only thing I don't understand is how anyone can not understand that.
- kazinator 3y agoThe point is that at the hardware level, arbitrary timings are in fact used. The same logic as usleep(100000); // give other thread enough time to do B is actually correct at the hardware level. Devices are expected to produce a stable output within some arbitrary time, that they meet. If they don't, a garbage value is blindly read anyway: there is no actual cause-and-effect synchronization other than adherence to the timing diagram's requirements.
- distcs 3y ago> Oh, yeah, the simple times before everybody learned that time is a local and observer-dependent measure. Modern computers do almost none time-based at-distance synchronization. This is a very odd response. Nothing you write here directly contradicts the parent comment and yet you seem to imply that you have a point that is the opposite of the parent comment. You seem to be going off on a tangent without addressing the main point that chips do depend on a clock firing periodically and that clock interval determining how long the circuitry waits for its pins to achieve a stable binary state before the next state transition. That was the original point of the parent comment and that point is still valid.