On Thu, Jan 15, 2009 at 12:37 AM, Tejun Heo <htejun@xxxxxxxxx> wrote: > Hello, > > James Bottomley wrote: >> I'm afraid that's pretty much marketing coolaid. Rotational storage >> will dominate for the forseeable future: just do a simple back of the >> envelope calculation: > > Or just compare prices per byte of memory, flash and rotation disk. > They haven't had changed too much during last several years. > Secondary storage which is only slightly cheaper than the primary > storage doesn't have much chance of flying high and far. > > Thanks. > > -- > tejun Have you seen the new pricing Samsung has announced for their 3rd generation SSD. It is about 1/3 of the Intel' SSD price if I recall correctly and the performance is approaching Intel's from what I've seen. I've been talking to the OpenHSM (Hierachical Storage Manager) team about their project. They are working on getting the logic in place now to move data blocks from one class of storage to another while leaving the filesystem itself un-affected from the users perspective. http://code.google.com/p/fscops/ They have a very long way to go with their code/project, but it is conceptually similar to the ext4_defrag patch that already exists. The big difference is the data block allocation algorithm will have to be totally different. If and when that get their code done, I would love to have 500 GB of SSD teamed with several TB of rotational HDD and have the HSM move my files between fast SSD and slow rotational. I typically know which datasets I will be working with heavily, so even a simple user space tool that would let me adjust which tier of storage my files were sitting on would suffice. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
