From: zwu.kernel@gmail.com
To: linux-btrfs@vger.kernel.org
Cc: viro@zeniv.linux.org.uk, sekharan@us.ibm.com,
linuxram@us.ibm.com, david@fromorbit.com,
chris.mason@fusionio.com, jbacik@fusionio.com,
idryomov@gmail.com, Martin@lichtvoll.de,
Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Subject: [RFC PATCH v2 1/5] BTRFS hot reloc, vfs: add one list_head field
Date: Fri, 21 Jun 2013 20:20:56 +0800 [thread overview]
Message-ID: <1371817260-8615-2-git-send-email-zwu.kernel@gmail.com> (raw)
In-Reply-To: <1371817260-8615-1-git-send-email-zwu.kernel@gmail.com>
From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Add one list_head field 'reloc_list' to accommodate
hot relocation support.
Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
---
fs/hot_tracking.c | 1 +
include/linux/hot_tracking.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/fs/hot_tracking.c b/fs/hot_tracking.c
index dbc90d4..f013182 100644
--- a/fs/hot_tracking.c
+++ b/fs/hot_tracking.c
@@ -44,6 +44,7 @@ static void hot_comm_item_init(struct hot_comm_item *ci, int type)
clear_bit(HOT_IN_LIST, &ci->delete_flag);
clear_bit(HOT_DELETING, &ci->delete_flag);
INIT_LIST_HEAD(&ci->track_list);
+ INIT_LIST_HEAD(&ci->reloc_list);
memset(&ci->hot_freq_data, 0, sizeof(struct hot_freq_data));
ci->hot_freq_data.avg_delta_reads = (u64) -1;
ci->hot_freq_data.avg_delta_writes = (u64) -1;
diff --git a/include/linux/hot_tracking.h b/include/linux/hot_tracking.h
index 1009377..98bb092 100644
--- a/include/linux/hot_tracking.h
+++ b/include/linux/hot_tracking.h
@@ -75,6 +75,7 @@ struct hot_comm_item {
unsigned long delete_flag;
struct rcu_head c_rcu;
struct list_head track_list; /* link to *_map[] */
+ struct list_head reloc_list; /* used in hot relocation*/
};
/* An item representing an inode and its access frequency */
--
1.7.11.7
next prev parent reply other threads:[~2013-06-21 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 12:20 [RFC PATCH v2 0/5] BTRFS hot relocation support zwu.kernel
2013-06-21 12:20 ` zwu.kernel [this message]
2013-06-21 12:20 ` [RFC PATCH v2 2/5] BTRFS hot reloc: add one new block group zwu.kernel
2013-06-21 12:20 ` [RFC PATCH v2 3/5] BTRFS hot reloc: add one hot reloc thread zwu.kernel
2013-06-21 12:20 ` [RFC PATCH v2 4/5] BTRFS hot reloc, procfs: add three proc interfaces zwu.kernel
2013-06-21 12:21 ` [RFC PATCH v2 5/5] BTRFS hot reloc: add hot relocation support zwu.kernel
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=1371817260-8615-2-git-send-email-zwu.kernel@gmail.com \
--to=zwu.kernel@gmail.com \
--cc=Martin@lichtvoll.de \
--cc=chris.mason@fusionio.com \
--cc=david@fromorbit.com \
--cc=idryomov@gmail.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=sekharan@us.ibm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wuzhy@linux.vnet.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).