Is block activity tracked exclusively by Bcache code or is Bcache piggy-backing on already existing statistics tracking that is implemented in LVM or the VM or (scsi?) block layers? If the first, I was wondering how hard it would be to move it into the lower levels and turned on/off with sysfs.
Is there a whitepaper that goes into the mechanics of the tracking, the granularity (eg. block region size), (de)promotion trigger logic, etc? Or is this a question best answered by "go read the code"? -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
