[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100727222916.GM18595@tracyreed.org>
Date: Tue, 27 Jul 2010 15:29:16 -0700
From: Tracy Reed <treed@...raviolet.org>
To: bchociej@...il.com
Cc: chris.mason@...cle.com, linux-btrfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, cmm@...ibm.com, bcchocie@...ibm.com,
mrlupfer@...ibm.com, crscott@...ibm.com,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/5] Btrfs: Add hot data tracking functionality
On Tue, Jul 27, 2010 at 05:00:18PM -0500, bchociej@...il.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.
--
Tracy Reed
http://tracyreed.org
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists