From: Ben Chociej <bchociej@gmail.com>
To: diegocg@gmail.com
Cc: chris.mason@oracle.com, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, cmm@us.ibm.com,
bcchocie@us.ibm.com, mrlupfer@us.ibm.com, crscott@us.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] Btrfs: Add hot data tracking functionality
Date: Tue, 27 Jul 2010 18:18:23 -0500 [thread overview]
Message-ID: <AANLkTi=x9q1XOu_6F2hOv_ZPoM+McKz9Nv2Q5GZNfa4a@mail.gmail.com> (raw)
In-Reply-To: <201007280110.46059.diegocg@gmail.com>
On Tue, Jul 27, 2010 at 6:10 PM, Diego Calleja <diegocg@gmail.com> wrot=
e:
> On Mi=E9rcoles, 28 de Julio de 2010 00:00:18 bchociej@gmail.com escri=
bi=F3:
>> 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 the=
se
>
> 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
WARNING: multiple messages have this Message-ID (diff)
From: Ben Chociej <bchociej@gmail.com>
To: diegocg@gmail.com
Cc: chris.mason@oracle.com, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, cmm@us.ibm.com,
bcchocie@us.ibm.com, mrlupfer@us.ibm.com, crscott@us.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] Btrfs: Add hot data tracking functionality
Date: Tue, 27 Jul 2010 18:18:23 -0500 [thread overview]
Message-ID: <AANLkTi=x9q1XOu_6F2hOv_ZPoM+McKz9Nv2Q5GZNfa4a@mail.gmail.com> (raw)
In-Reply-To: <201007280110.46059.diegocg@gmail.com>
On Tue, Jul 27, 2010 at 6:10 PM, Diego Calleja <diegocg@gmail.com> wrote:
> On Miércoles, 28 de Julio de 2010 00:00:18 bchociej@gmail.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
next prev parent reply other threads:[~2010-07-27 23:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 22:00 [RFC PATCH 0/5] Btrfs: Add hot data tracking functionality bchociej
2010-07-27 22:00 ` [RFC PATCH 1/5] Btrfs: Add experimental hot data hash list index bchociej
2010-07-27 22:00 ` [RFC PATCH 2/5] Btrfs: Add data structures for hot data tracking bchociej
2010-07-27 22:00 ` [RFC PATCH 3/5] Btrfs: 3 new ioctls related to hot data features bchociej
2010-07-27 22:00 ` [RFC PATCH 4/5] Btrfs: Add debugfs interface for hot data stats bchociej
2010-07-27 22:00 ` [RFC PATCH 5/5] Btrfs: Add hooks to enable hot data tracking bchociej
2010-07-27 22:29 ` [RFC PATCH 0/5] Btrfs: Add hot data tracking functionality Tracy Reed
2010-07-28 21:22 ` Mingming Cao
2010-07-27 23:10 ` Diego Calleja
2010-07-27 23:10 ` Diego Calleja
2010-07-27 23:10 ` Diego Calleja
2010-07-27 23:18 ` Ben Chociej [this message]
2010-07-27 23:18 ` Ben Chociej
2010-07-28 12:28 ` Chris Samuel
2010-07-27 23:38 ` Christian Stroetmann
2010-07-28 22:00 ` Mingming Cao
2010-07-29 12:17 ` Dave Chinner
2010-07-29 13:17 ` Christian Stroetmann
2010-08-04 17:40 ` Mingming Cao
2010-08-04 18:44 ` Christian Stroetmann
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='AANLkTi=x9q1XOu_6F2hOv_ZPoM+McKz9Nv2Q5GZNfa4a@mail.gmail.com' \
--to=bchociej@gmail.com \
--cc=bcchocie@us.ibm.com \
--cc=chris.mason@oracle.com \
--cc=cmm@us.ibm.com \
--cc=crscott@us.ibm.com \
--cc=diegocg@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrlupfer@us.ibm.com \
/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.