Re:HN is up again
by gomijacogeo on Sunday July 10, 2022 @04:59AM
(#32042969)
It might not be nanoseconds, but something that's a power of 2 number of nanoseconds going into an appropriately small container seems likely. For example, a 62.5MHz counter going into 53 bits breaks at the same limit. Why 53 bits? That's where things start to get weird with IEEE doubles - adding 1 no longer fits into the mantissa and the number doesn't change. So maybe someone was doing a bit of fp math to figure out the time or schedule a next event? Anyway, very likely some kind of clock math that wrapped or saturated and broke a fundamental assumption.
[ Parent
| on HN ]
Re:HN is up again
by dreamcompiler on Sunday July 10, 2022 @08:31PM
(#32050799)
53 is indeed a magic value for IEEE doubles, but why would anybody count an inherently integer value with floating-point? That's a serious rookie mistake.
Of course there's no law that says SSD firmware writers can't be rookies.
Re:HN is up again
by lultimouomo on Monday July 11, 2022 @02:49AM
(#32053048)
Full stack JS, everything is a double down to the SSD firmware!