On Tue, 2010-07-27 at 15:29 -0700, Tracy Reed wrote: > On Tue, Jul 27, 2010 at 05:00:18PM -0500, bchoc...@gmail.com spake thusly: > > The long-term goal of these patches, as discussed in the Motivation > > section at the end of this message, is to enable Btrfs to perform > > automagic relocation of hot data to fast media like SSD. This goal has > > been motivated by the Project Ideas page on the Btrfs wiki. > > With disks being so highly virtualized away these days is there any > way for btrfs to know which are the fast outer-tracks vs the slower > inner-tracks of a physical disk? If so not only could this benefit SSD > owners but it could also benefit the many more spinning platters out > there. If not (which wouldn't be surprising) then disregard. Even just > having that sort of functionality for SSD would be excellent. If I > understand correctly not only would this work for SSD but if I have a > SAN full of many large 7200rpm disks and a few 15k SAS disks I could > effectively utilize that disk by allowing btrfs to place hot data on > the 15k SAS. I understand Compellent does this as well. >
This certainly possible. The disk to store hot data does not has to limit to SSDs, thought current implementation detecting "fast" device by checking the SSD rotation flag. This could be easily extended if btrfs is able to detect the relatively fast devices. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
