From: bchociej@gmail.com
To: chris.mason@oracle.com, linux-btrfs@vger.kernel.org
Cc: 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, bchociej@gmail.com, mlupfer@gmail.com,
conscott@vt.edu
Subject: [PATCH 0/2] Btrfs-progs: Add support for hot data migration
Date: Thu, 12 Aug 2010 17:29:35 -0500 [thread overview]
Message-ID: <1281652177-23562-1-git-send-email-bchociej@gmail.com> (raw)
This patch set introduces functionality into btrfsctl and mkfs.btrfs to
support the kernel patches for hot data tracking and migration to SSD
with Btrfs. New functionality includes a -h option to mkfs.btrfs to
preallocate approrpiate block group types for SSD data migration, and
also includes additional options for btrfsctl to interact with the new
ioctls introduced by the kernel patches.
DIFFSTAT:
btrfsctl.c | 111 +++++++++++++++++++++++++++++++++++++++-
ctree.h | 2 +
extent-tree.c | 2 +-
ioctl-test.c | 3 +
ioctl.h | 24 +++++++++
mkfs.c | 131 ++++++++++++++++++++++++++++++++++++++++-------
utils.c | 1 +
volumes.c | 73 +++++++++++++++++++++++++-
volumes.h | 3 +-
9 files changed, 326 insertions(+), 24 deletions(-)
Signed-off-by: Ben Chociej <bchociej@gmail.com>
Signed-off-by: Matt Lupfer <mlupfer@gmail.com>
Tested-by: Conor Scott <conscott@vt.edu>
next reply other threads:[~2010-08-12 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 22:29 bchociej [this message]
2010-08-12 22:29 ` [PATCH 1/2] Btrfs-progs: Add support for hot data ioctls bchociej
2010-08-12 22:29 ` [PATCH 2/2] Btrfs-progs: Add hot data support in mkfs bchociej
2010-08-13 13:14 ` Andrey Panin
2010-08-13 14:08 ` Tomasz Torcz
2010-08-13 14:12 ` Ben Chociej
2010-08-13 14:10 ` Ben Chociej
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=1281652177-23562-1-git-send-email-bchociej@gmail.com \
--to=bchociej@gmail.com \
--cc=bcchocie@us.ibm.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 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).