Dear bcache-developers,
This is a feature request for a very specific use case:
Having a caching device in front of an md-raid on a machine which
serves as a low power media server.
The last writes could be cached on the caching device to reduce the
non-sleep time of the raid (drives in spindown state) while playing
media, together with a huge writeback delay of, let's say, 3 hours,
newest media would always be read from the caching device.
It's not likely that a recently read (watched) media file will be read
again after having been read before (very recently), but it's very
likely that it'll be read once after it was written.
I could disable sequential_cutoff or set it rediculously high. That
would result in every sequential read being cached into the caching
device, too, which in this use case is not wanted.
Could you split up the sequential_cutoff setting to
sequential_read_cutoff and sequential_write_cutoff?
That way writes including sequential ones can be cached for later, but
sequential reads could be ignored by the cache.
Thank you in advance
Hannes
--
Hannes Tismer
Herzogstr. 4
41238 Mönchengladbach
--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
