From: Christian Stroetmann <stroetmann@ontolinux.com>
To: Dave Chinner <david@fromorbit.com>,
Minming Cao <bchociej@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/5] Btrfs: Add hot data tracking functionality
Date: Thu, 29 Jul 2010 15:17:13 +0200 [thread overview]
Message-ID: <4C517F59.5060507@ontolinux.com> (raw)
In-Reply-To: <20100729121729.GK655@dastard>
Aloha Mingming, Aloha Dave;
On the 29.07.2010 14:17, Dave Chinner wrote:
> On Wed, Jul 28, 2010 at 03:00:48PM -0700, Mingming Cao wrote:
>
>> On Wed, 2010-07-28 at 01:38 +0200, Christian Stroetmann wrote:
>>
>>> At the 28.07.2010 00:00, Ben Chociej wrote:
>>> Wouldn't this feature be useful for other file systems as well, so that
>>> a more general and not an only Btrfs related solution is preferable?
>>>
>>>
>> Would certainly nice to add this feature to all filesystem, but right
>> now btrfs is the only fs which have multiple device support in itself.
>>
>
Thanks for your explanation, Mingming. And I had further questions to
this point, but didn't know exactly how to formulate them in a short
way. But luckily Dave has a possible solution that is related with my
questions around the multiple device feature of Btrfs and hot data handling.
> Why does it even need multiple devices in the filesystem?
Yes, that was the point I asked myself after reading about this in the
Btrfs wiki
(https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices)
and how ZFS does it.
> All the
> filesystem needs to know is the relative speed of regions of it's
> block address space and to be provided allocation hints. everything
> else is just movement of data. You could keep the speed information
> in the device mapper table and add an interface for filesystems to
> query it, and then you've got infrastructure that all filesystems
> could hook into.
>
Yes indeed, something like this general solution that doesn't need the
multiple device feature at all.
> The tracking features dont' appear to have anything btrfs specific
> in them, so t iseems wrong to implement it there just because you're
> only looking at btrfs' method of tracking multiple block devices
> and moving blocks....
>
> Cheers,
>
> Dave.
>
Thank you very much for being creative. :D
Cheerio
Christian *<:o) O>-< -(D)>-<
next prev parent reply other threads:[~2010-07-29 13:17 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
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 [this message]
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=4C517F59.5060507@ontolinux.com \
--to=stroetmann@ontolinux.com \
--cc=bchociej@gmail.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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).