[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100813131422.GA615@centrinvest.ru>
Date: Fri, 13 Aug 2010 17:14:22 +0400
From: "Andrey Panin" <pazke@...trinvest.ru>
To: bchociej@...il.com
Cc: chris.mason@...cle.com, linux-btrfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
cmm@...ibm.com, bcchocie@...ibm.com, mrlupfer@...ibm.com,
crscott@...ibm.com, mlupfer@...il.com, conscott@...edu
Subject: Re: [PATCH 2/2] Btrfs-progs: Add hot data support in mkfs
On 224, 08 12, 2010 at 05:29:37PM -0500, bchociej@...il.com wrote:
> From: Ben Chociej <bchociej@...il.com>
>
> Modified mkfs.btrfs to add hot data relocation option (-h) which
> preallocates BTRFS_BLOCK_GROUP_DATA_SSD and
> BTRFS_BLOCK_GROUP_METADATA_SSD at mkfs time for future use by hot data
> relocation code. Also added a userspace function to detect whether a
> block device is an SSD by reading the sysfs block queue rotational flag.
IMHO this policy is too inflexible. What if I have large array of slow SATA
disks and some fast SAS ones ?
--
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