zwu.kernel@xxxxxxxxx <zwu.kernel@xxxxxxxxx> schrieb: > The patchset is trying to introduce hot relocation support > for BTRFS. In hybrid storage environment, when the data in > HDD disk get hot, it can be relocated to SSD disk by BTRFS > hot relocation support automatically; also, if SSD disk ratio > exceed its upper threshold, the data which get cold can be > looked up and relocated to HDD disk to make more space in SSD > disk at first, and then the data which get hot will be relocated > to SSD disk automatically. How will it compare to bcache? I'm currently thinking about buying an SSD but bcache requires some efforts in migrating the storage to use. And after all those hassles I am even not sure if it would work easily with a dracut generated initramfs. Bcache seems to be quite clever with its approach. This one looks completely different and more targetted to relocate data which is used often instead of trying to reduce head movement. I'm quite happy with the throuput of my 3x HDD btrfs pool (according to bootchart up to 600 MB/s during boot). A single SSD would be slower since head movement seems not to be the issue during boot. Will this patch relocate such data? Or does it try to relocate only data which requires random head movement? Thanks, Kai -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
