From: Diego Calleja <diegocg@gmail.com>
To: bchociej@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: Wed, 28 Jul 2010 01:10:45 +0200 [thread overview]
Message-ID: <201007280110.46059.diegocg@gmail.com> (raw)
In-Reply-To: <1280268023-18408-1-git-send-email-bchociej@gmail.com>
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?
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-27 23:11 UTC|newest]
Thread overview: 17+ 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 [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=201007280110.46059.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=bcchocie@us.ibm.com \
--cc=bchociej@gmail.com \
--cc=chris.mason@oracle.com \
--cc=cmm@us.ibm.com \
--cc=crscott@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).