Where I think the overlaid CRCs might become more interesting is when the CRC is supposed to cover a fairly large block (say 64K) but you're rewriting a much smaller piece (say 4K) with a minor update. If you don't have the other pieces handy, you can compute your CRC update on just the piece you have, rather than having to go read them.
Posted Apr 6, 2012 23:02 UTC (Fri) by dlang (✭ supporter ✭, #313)
[Link]
true, but if you think of the fact that it's only the on-device controller that would have to re-read the data, I don't think it really matters, the speed that it can re-read the raw data is fast enough that I really don't expect it to be a bottleneck.