On Mon, 2010-08-30 at 08:42 +0800, Hubert Kario wrote: > On Thursday 26 of August 2010 04:13:43 Shaohua Li wrote: > > On Fri, Aug 13, 2010 at 06:22:00AM +0800, bchociej@xxxxxxxxx wrote: > > > - Hooks in existing Btrfs functions to track data access frequency > > > > > > (btrfs_direct_IO, btrfs_readpages, and extent_write_cache_pages) > > > > > > - New rbtrees for tracking access frequency of inodes and sub-file > > > > > > ranges (hotdata_map.c) > > > > > > - A hash list for indexing data by its temperature (hotdata_hash.c) > > > > > > - A debugfs interface for dumping data from the rbtrees (debugfs.c) > > > > > > - A background kthread for relocating data to faster media based on > > > > > > temperature > > > > Hi, > > I'm wondering if the temperature info can be exported to userspace, and > > let a daemon to do the relocation (by ioctl). A userspace daemon is more > > flexible. > > Flexibility of userspace daemon is one thing, the ability to let the admin > precisely control on which drive data is placed could be really beneficial in > some scenarios is another thing. > > This would also allow online defragmentation, together with access to > statistics, one that (for quick runs) has really good time/performance benefit > ratio. Agreed, I'm thinking of the online defragmentation based on hot access too. Btrfs usually has more fragment. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
