Comment by nolist_policy
2 years ago
> If a host tried to flush after every write to force the latter behavior, it would end up with the same problem.
So? No reason to break the contract that flush makes all submitted writes durable. The drive can compact space in the background.
Yes, GC should be smart enough to free up space from padding. But then there's a write amplification penalty and meeting endurance specifications is impossible. A padded write already carries a write amplification >1, then GC needs to be invoked much more frequently on top of that to drive it even higher. With pathological Flush usage, you have to pick your poison. Run out of space, run out of SSD life.