Christopher Haster 425dc810a5 Modified robekras's optimization to avoid flush for all seeks in cache ...

The basic idea is simple, if we seek to a position in the currently
loaded cache, don't flush the cache. Notably this ensures that seek is
always as fast or faster than just reading the data.

This is a bit tricky since we need to check that our new block and
offset match the cache, fortunately we can skip the block check by
reevaluating the block index for both the current and new positions.

Note this only works whene reading, for writing we need to always flush
the cache, or else we will lose the pending write data.

2022-04-10 12:46:51 -05:00

158 KiB

Raw Blame History

View Raw