3 ms·
The requirement request is a great way to push back on feature creep. There's a lot of cargo culting that goes on in the "protection against bit-flips". You som
by russdill 8y ago
The requirement request is a great way to push back on feature creep. There's a lot of cargo culting that goes on in the "protection against bit-flips". You sometimes have to go a step further and ask what error rate are you required to be below. Once you have that number, you can start asking what your current error rate is without mitigations, and how much a given mitigation will reduce your error rate.
- vvanders 8y agoMy favorite entry in that problem space is metastability[1]. Do you interface two different clock domains(which is basically most things)? Guess what all of your computing is built on the "chance" that bits won't flip. Granted, statistics make this pretty solid but kinda blew my mind when I first stumbled across it. [1] https://en.wikipedia.org/wiki/Metastability_(electronics) https://en.wikipedia.org/wiki/Metastability_(electronics)
- russdill 8y agoYup, a large portion of hardware design is based on getting below a required maximum failure rate. For metastability, you just keep adding more flip-flops. BTW, the cache invalidation request may be due to this. They figured they could more easily reach their time between failure interval if they could discount time during S1.
- drharby 8y agoHurray digital signal synchronization!