[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=x9q1XOu_6F2hOv_ZPoM+McKz9Nv2Q5GZNfa4a@mail.gmail.com>
Date: Tue, 27 Jul 2010 18:18:23 -0500
From: Ben Chociej <bchociej@...il.com>
To: diegocg@...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 6:10 PM, Diego Calleja <diegocg@...il.com> wrote:
> On Miércoles, 28 de Julio de 2010 00:00:18 bchociej@...il.com escribió:
>> With Btrfs's COW approach, an external cache (where data is moved to
>> SSD, rather than just cached there) makes a lot of sense. Though these
>
> As I understand it, what your proyect intends to do is to move "hot"
> data to a SSD which would be part of a Btrfs pool, and not do any
> kind of SSD caching, as bcache (http://lwn.net/Articles/394672/) does?
>
Yes, that's correct. It's likely not going to be a cache in the
traditional sense, since the entire capacity of both HDD and SSD would
be available.
BC
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists