How does this work at a physical level?

Posted Feb 23, 2025 13:01 UTC (Sun) by farnz (subscriber, #17727)
In reply to: How does this work at a physical level? by KJ7RRV
Parent article: Support for atomic block writes in 6.13

It doesn't need a capacitor, necessarily. There's two routes you can take in an SSD to enable this feature:

Have a capacitor or other energy store on the device, so that when power is lost, you can complete all the writes before the energy store drains.
Use the FTL's block mapping to allow you to atomically switch in a new mapping with a single bit write, and do not return that the command is complete until the new mapping is switched in. Then, you can write the new data and associated mapping, followed by the single bit write to switch the mapping over. If that bit write succeeds, the swap over is done; if it doesn't, the swap fails to happen.

Capacitor is more likely, because it lets you have a write cache, too, and thus a performance advantage in enterprise drives. But it's possible without one in an SSD.

How does this work at a physical level?

Posted Feb 24, 2025 1:32 UTC (Mon) by Paf (subscriber, #91811) [Link] (1 responses)

"Use the FTL's block mapping to allow you to atomically switch in a new mapping with a single bit write, and do not return that the command is complete until the new mapping is switched in. Then, you can write the new data and associated mapping, followed by the single bit write to switch the mapping over. If that bit write succeeds, the swap over is done; if it doesn't, the swap fails to happen."

I like that this is basically double writes - sometimes, it's turtles all the way down.

How does this work at a physical level?

Posted Mar 3, 2025 17:09 UTC (Mon) by mebrown (subscriber, #7960) [Link]

No, it's not a double write.

The new data is written to a new block, then the mapping table entry is atomically switched so that the old data is unmapped/freed and the new data is swapped in.