From: "Andrey Panin" <pazke@centrinvest.ru>
To: bchociej@gmail.com
Cc: chris.mason@oracle.com, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
cmm@us.ibm.com, bcchocie@us.ibm.com, mrlupfer@us.ibm.com,
crscott@us.ibm.com, mlupfer@gmail.com, conscott@vt.edu
Subject: Re: [PATCH 2/2] Btrfs-progs: Add hot data support in mkfs
Date: Fri, 13 Aug 2010 17:14:22 +0400 [thread overview]
Message-ID: <20100813131422.GA615@centrinvest.ru> (raw)
In-Reply-To: <1281652177-23562-3-git-send-email-bchociej@gmail.com>
On 224, 08 12, 2010 at 05:29:37PM -0500, bchociej@gmail.com wrote:
> From: Ben Chociej <bchociej@gmail.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 ?
next prev parent reply other threads:[~2010-08-13 13:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 22:29 [PATCH 0/2] Btrfs-progs: Add support for hot data migration bchociej
2010-08-12 22:29 ` [PATCH 1/2] Btrfs-progs: Add support for hot data ioctls bchociej
2010-08-13 16:44 ` Goffredo Baroncelli
2010-08-12 22:29 ` [PATCH 2/2] Btrfs-progs: Add hot data support in mkfs bchociej
2010-08-13 13:14 ` Andrey Panin [this message]
2010-08-13 14:08 ` Tomasz Torcz
2010-08-13 14:12 ` Ben Chociej
2010-08-13 14:12 ` Ben Chociej
2010-08-13 14:12 ` Ben Chociej
2010-08-13 14:10 ` Ben Chociej
2010-08-13 14:10 ` Ben Chociej
2010-08-13 14:10 ` Ben Chociej
2010-09-01 11:56 ` Hubert Kario
2010-09-01 11:56 ` Hubert Kario
2010-09-01 11:56 ` Hubert Kario
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=20100813131422.GA615@centrinvest.ru \
--to=pazke@centrinvest.ru \
--cc=bcchocie@us.ibm.com \
--cc=bchociej@gmail.com \
--cc=chris.mason@oracle.com \
--cc=cmm@us.ibm.com \
--cc=conscott@vt.edu \
--cc=crscott@us.ibm.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlupfer@gmail.com \
--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.