From: "Matias Bjørling" <m@bjorling.me>
To: Alex Elsayed <eternaleye@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Hybrid Storage proposal
Date: Thu, 21 Feb 2013 10:25:15 +0100 [thread overview]
Message-ID: <5125E7FB.6020502@bjorling.me> (raw)
In-Reply-To: <kg37js$5vc$1@ger.gmane.org>
On 02/20/2013 08:19 PM, Alex Elsayed wrote:
> Matias Bjorling wrote:
>
>> Here is a short proposal for the hybrid storage cache idea with
>> introduction/motivation and a bird's eye view of an approach to implement
>> a hybrid storage cache for btrfs. Please note that there is currently no
>> available patches. We would like to get as much input before as possible
>> before we start designing and implementing a solution.
>
> Just to toss this out there, aside from the option of 'cache chunks' there
> is the option of using normal chunks, and instead place extents on chunks
> based on performance characteristics of the underlying device.
>
> As an analogy, if the above proposal is closer to the 'bcache' approach of
> treating the SSD purely as a performance enhancer that does not contribute
> to capacity, performance-based allocation is closer to the 'btier' [1]
> approach in which the SSD does contribute to capacity, but has 'dibs' on
> performance-sensitive data.
>
> [1] Btier sourceforge page: http://sourceforge.net/projects/tier/
>
> Lessfs homepage, with btier info: http://www.lessfs.com/wordpress/
Good point. I think both approaches are relatively easy to combine.
next prev parent reply other threads:[~2013-02-21 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 16:46 Hybrid Storage proposal Matias Bjorling
2013-02-20 19:19 ` Alex Elsayed
2013-02-21 9:25 ` Matias Bjørling [this message]
2013-02-21 0:49 ` Gareth Pye
2013-02-21 6:53 ` Alex Elsayed
2013-02-26 11:04 ` Zhi Yong Wu
2013-02-26 13:08 ` [POSSIBLE SPAM] " Matias Bjørling
2013-02-27 11:50 ` Zhi Yong Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5125E7FB.6020502@bjorling.me \
--to=m@bjorling.me \
--cc=eternaleye@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.