Date: Thu, 29 Jul 2010 22:17:29 +1000
From: Dave Chinner <david@fromorbit.com>
To: Mingming Cao <cmm@us.ibm.com>
Cc: Christian Stroetmann <stroetmann@ontolinux.com>, 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
Message-ID: <20100729121729.GK655@dastard>
References: <1280268023-18408-1-git-send-email-bchociej@gmail.com>
 <4C4F6DF2.6090905@ontolinux.com>
 <1280354448.7694.4.camel@mingming-laptop>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1280354448.7694.4.camel@mingming-laptop>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1420
Lines: 34

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.

Why does it even need multiple devices in the filesystem? 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.

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.
-- 
Dave Chinner
david@fromorbit.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/