From: Zhi Yong Wu <zwu.kernel@gmail.com> To: "Lukáš Czerner" <lczerner@redhat.com> Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org, linuxram@linux.vnet.ibm.com, viro@zeniv.linux.org.uk, david@fromorbit.com, dave@jikos.cz, tytso@mit.edu, cmm@us.ibm.com, Zhi Yong Wu <wuzhy@linux.vnet.ibm.com> Subject: Re: [RFC v3 01/13] btrfs: add one new mount option '-o hot_track' Date: Wed, 10 Oct 2012 20:21:48 +0800 [thread overview] Message-ID: <CAEH94LgG+F2B=uw4tT1nYrZuq1ot3Sy19JjvSekZbUu4V=oOdA@mail.gmail.com> (raw) In-Reply-To: <5075632c.03cc440a.1b33.7805SMTPIN_ADDED@mx.google.com> On Wed, Oct 10, 2012 at 7:59 PM, Lukáš Czerner <lczerner@redhat.com> wrote: > On Wed, 10 Oct 2012, zwu.kernel@gmail.com wrote: > >> Date: Wed, 10 Oct 2012 18:07:23 +0800 >> From: zwu.kernel@gmail.com >> To: linux-fsdevel@vger.kernel.org >> Cc: linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org, >> linux-kernel@vger.kernel.org, linuxram@linux.vnet.ibm.com, >> viro@zeniv.linux.org.uk, david@fromorbit.com, dave@jikos.cz, >> tytso@mit.edu, cmm@us.ibm.com, Zhi Yong Wu <wuzhy@linux.vnet.ibm.com> >> Subject: [RFC v3 01/13] btrfs: add one new mount option '-o hot_track' >> >> From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com> >> >> Introduce one new mount option '-o hot_track', >> and add its parsing support. >> Its usage looks like: >> mount -o hot_track >> mount -o nouser,hot_track >> mount -o nouser,hot_track,loop >> mount -o hot_track,nouser > > This patch should probably be at the end of the series. Can you let me know your reason? I think that it is not necessary to be at the end of the series. > > -Lukas > >> >> Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com> >> --- >> fs/btrfs/ctree.h | 1 + >> fs/btrfs/super.c | 7 ++++++- >> 2 files changed, 7 insertions(+), 1 deletions(-) >> >> diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h >> index 9821b67..094bec6 100644 >> --- a/fs/btrfs/ctree.h >> +++ b/fs/btrfs/ctree.h >> @@ -1726,6 +1726,7 @@ struct btrfs_ioctl_defrag_range_args { >> #define BTRFS_MOUNT_CHECK_INTEGRITY (1 << 20) >> #define BTRFS_MOUNT_CHECK_INTEGRITY_INCLUDING_EXTENT_DATA (1 << 21) >> #define BTRFS_MOUNT_PANIC_ON_FATAL_ERROR (1 << 22) >> +#define BTRFS_MOUNT_HOT_TRACK (1 << 23) >> >> #define btrfs_clear_opt(o, opt) ((o) &= ~BTRFS_MOUNT_##opt) >> #define btrfs_set_opt(o, opt) ((o) |= BTRFS_MOUNT_##opt) >> diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c >> index 83d6f9f..00be9e3 100644 >> --- a/fs/btrfs/super.c >> +++ b/fs/btrfs/super.c >> @@ -41,6 +41,7 @@ >> #include <linux/slab.h> >> #include <linux/cleancache.h> >> #include <linux/ratelimit.h> >> +#include <linux/hot_tracking.h> >> #include "compat.h" >> #include "delayed-inode.h" >> #include "ctree.h" >> @@ -303,7 +304,7 @@ enum { >> Opt_notreelog, Opt_ratio, Opt_flushoncommit, Opt_discard, >> Opt_space_cache, Opt_clear_cache, Opt_user_subvol_rm_allowed, >> Opt_enospc_debug, Opt_subvolrootid, Opt_defrag, Opt_inode_cache, >> - Opt_no_space_cache, Opt_recovery, Opt_skip_balance, >> + Opt_no_space_cache, Opt_recovery, Opt_skip_balance, Opt_hot_track, >> Opt_check_integrity, Opt_check_integrity_including_extent_data, >> Opt_check_integrity_print_mask, Opt_fatal_errors, >> Opt_err, >> @@ -342,6 +343,7 @@ static match_table_t tokens = { >> {Opt_no_space_cache, "nospace_cache"}, >> {Opt_recovery, "recovery"}, >> {Opt_skip_balance, "skip_balance"}, >> + {Opt_hot_track, "hot_track"}, >> {Opt_check_integrity, "check_int"}, >> {Opt_check_integrity_including_extent_data, "check_int_data"}, >> {Opt_check_integrity_print_mask, "check_int_print_mask=%d"}, >> @@ -553,6 +555,9 @@ int btrfs_parse_options(struct btrfs_root *root, char *options) >> case Opt_skip_balance: >> btrfs_set_opt(info->mount_opt, SKIP_BALANCE); >> break; >> + case Opt_hot_track: >> + btrfs_set_opt(info->mount_opt, HOT_TRACK); >> + break; >> #ifdef CONFIG_BTRFS_FS_CHECK_INTEGRITY >> case Opt_check_integrity_including_extent_data: >> printk(KERN_INFO "btrfs: enabling check integrity" >> -- Regards, Zhi Yong Wu
WARNING: multiple messages have this Message-ID (diff)
From: Zhi Yong Wu <zwu.kernel@gmail.com> To: "Lukáš Czerner" <lczerner@redhat.com> Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org, linuxram@linux.vnet.ibm.com, viro@zeniv.linux.org.uk, david@fromorbit.com, dave@jikos.cz, tytso@mit.edu, cmm@us.ibm.com, Zhi Yong Wu <wuzhy@linux.vnet.ibm.com> Subject: Re: [RFC v3 01/13] btrfs: add one new mount option '-o hot_track' Date: Wed, 10 Oct 2012 20:21:48 +0800 [thread overview] Message-ID: <CAEH94LgG+F2B=uw4tT1nYrZuq1ot3Sy19JjvSekZbUu4V=oOdA@mail.gmail.com> (raw) In-Reply-To: <5075632c.03cc440a.1b33.7805SMTPIN_ADDED@mx.google.com> On Wed, Oct 10, 2012 at 7:59 PM, Lukáš Czerner <lczerner@redhat.com> wrote: > On Wed, 10 Oct 2012, zwu.kernel@gmail.com wrote: > >> Date: Wed, 10 Oct 2012 18:07:23 +0800 >> From: zwu.kernel@gmail.com >> To: linux-fsdevel@vger.kernel.org >> Cc: linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org, >> linux-kernel@vger.kernel.org, linuxram@linux.vnet.ibm.com, >> viro@zeniv.linux.org.uk, david@fromorbit.com, dave@jikos.cz, >> tytso@mit.edu, cmm@us.ibm.com, Zhi Yong Wu <wuzhy@linux.vnet.ibm.com> >> Subject: [RFC v3 01/13] btrfs: add one new mount option '-o hot_track' >> >> From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com> >> >> Introduce one new mount option '-o hot_track', >> and add its parsing support. >> Its usage looks like: >> mount -o hot_track >> mount -o nouser,hot_track >> mount -o nouser,hot_track,loop >> mount -o hot_track,nouser > > This patch should probably be at the end of the series. Can you let me know your reason? I think that it is not necessary to be at the end of the series. > > -Lukas > >> >> Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com> >> --- >> fs/btrfs/ctree.h | 1 + >> fs/btrfs/super.c | 7 ++++++- >> 2 files changed, 7 insertions(+), 1 deletions(-) >> >> diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h >> index 9821b67..094bec6 100644 >> --- a/fs/btrfs/ctree.h >> +++ b/fs/btrfs/ctree.h >> @@ -1726,6 +1726,7 @@ struct btrfs_ioctl_defrag_range_args { >> #define BTRFS_MOUNT_CHECK_INTEGRITY (1 << 20) >> #define BTRFS_MOUNT_CHECK_INTEGRITY_INCLUDING_EXTENT_DATA (1 << 21) >> #define BTRFS_MOUNT_PANIC_ON_FATAL_ERROR (1 << 22) >> +#define BTRFS_MOUNT_HOT_TRACK (1 << 23) >> >> #define btrfs_clear_opt(o, opt) ((o) &= ~BTRFS_MOUNT_##opt) >> #define btrfs_set_opt(o, opt) ((o) |= BTRFS_MOUNT_##opt) >> diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c >> index 83d6f9f..00be9e3 100644 >> --- a/fs/btrfs/super.c >> +++ b/fs/btrfs/super.c >> @@ -41,6 +41,7 @@ >> #include <linux/slab.h> >> #include <linux/cleancache.h> >> #include <linux/ratelimit.h> >> +#include <linux/hot_tracking.h> >> #include "compat.h" >> #include "delayed-inode.h" >> #include "ctree.h" >> @@ -303,7 +304,7 @@ enum { >> Opt_notreelog, Opt_ratio, Opt_flushoncommit, Opt_discard, >> Opt_space_cache, Opt_clear_cache, Opt_user_subvol_rm_allowed, >> Opt_enospc_debug, Opt_subvolrootid, Opt_defrag, Opt_inode_cache, >> - Opt_no_space_cache, Opt_recovery, Opt_skip_balance, >> + Opt_no_space_cache, Opt_recovery, Opt_skip_balance, Opt_hot_track, >> Opt_check_integrity, Opt_check_integrity_including_extent_data, >> Opt_check_integrity_print_mask, Opt_fatal_errors, >> Opt_err, >> @@ -342,6 +343,7 @@ static match_table_t tokens = { >> {Opt_no_space_cache, "nospace_cache"}, >> {Opt_recovery, "recovery"}, >> {Opt_skip_balance, "skip_balance"}, >> + {Opt_hot_track, "hot_track"}, >> {Opt_check_integrity, "check_int"}, >> {Opt_check_integrity_including_extent_data, "check_int_data"}, >> {Opt_check_integrity_print_mask, "check_int_print_mask=%d"}, >> @@ -553,6 +555,9 @@ int btrfs_parse_options(struct btrfs_root *root, char *options) >> case Opt_skip_balance: >> btrfs_set_opt(info->mount_opt, SKIP_BALANCE); >> break; >> + case Opt_hot_track: >> + btrfs_set_opt(info->mount_opt, HOT_TRACK); >> + break; >> #ifdef CONFIG_BTRFS_FS_CHECK_INTEGRITY >> case Opt_check_integrity_including_extent_data: >> printk(KERN_INFO "btrfs: enabling check integrity" >> -- Regards, Zhi Yong Wu -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-10-10 12:21 UTC|newest] Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-10 10:07 [RFC v3 00/13] vfs: hot data tracking zwu.kernel 2012-10-10 10:07 ` [RFC v3 01/13] btrfs: add one new mount option '-o hot_track' zwu.kernel [not found] ` <5075632c.03cc440a.1b33.7805SMTPIN_ADDED@mx.google.com> 2012-10-10 12:21 ` Zhi Yong Wu [this message] 2012-10-10 12:21 ` Zhi Yong Wu 2012-10-10 13:11 ` Lukáš Czerner 2012-10-10 13:16 ` Zhi Yong Wu 2012-10-10 16:28 ` David Sterba 2012-10-11 13:41 ` Zhi Yong Wu 2012-10-11 14:35 ` Zhi Yong Wu 2012-10-11 14:41 ` David Sterba 2012-10-11 14:46 ` Zhi Yong Wu 2012-10-10 10:07 ` [RFC v3 02/13] vfs: introduce private radix tree structures zwu.kernel 2012-10-10 15:34 ` David Sterba 2012-10-11 13:35 ` Zhi Yong Wu 2012-10-10 10:07 ` [RFC v3 03/13] vfs: Initialize and free main data structures zwu.kernel 2012-10-10 10:07 ` [RFC v3 04/13] vfs: add function for collecting raw access info zwu.kernel 2012-10-10 10:07 ` [RFC v3 05/13] vfs: add two map arrays zwu.kernel 2012-10-10 10:07 ` [RFC v3 06/13] vfs: add hooks to enable hot data tracking zwu.kernel 2012-10-10 10:07 ` [RFC v3 07/13] vfs: add function for updating map arrays zwu.kernel 2012-10-10 10:07 ` [RFC v3 08/13] vfs: add aging function for old map info zwu.kernel 2012-10-10 10:07 ` [RFC v3 09/13] vfs: add one wq to update map info periodically zwu.kernel 2012-10-16 0:27 ` Dave Chinner 2012-10-17 6:34 ` Zhi Yong Wu 2012-10-18 2:25 ` Zheng Liu 2012-10-18 2:26 ` Zhi Yong Wu 2012-10-10 10:07 ` [RFC v3 10/13] vfs: register one memory shrinker zwu.kernel 2012-10-10 10:07 ` [RFC v3 11/13] vfs: add 3 new ioctl interfaces zwu.kernel 2012-10-15 7:48 ` Dave Chinner 2012-10-15 7:57 ` Zhi Yong Wu 2012-10-16 3:17 ` Dave Chinner 2012-10-16 4:18 ` Zhi Yong Wu 2012-10-19 8:21 ` Zhi Yong Wu 2012-10-10 10:07 ` [RFC v3 12/13] vfs: add debugfs support zwu.kernel 2012-10-10 16:53 ` David Sterba 2012-10-10 21:05 ` David Sterba 2012-10-15 7:55 ` Dave Chinner 2012-10-15 8:15 ` Zhi Yong Wu 2012-10-15 8:04 ` Dave Chinner 2012-10-15 8:47 ` Zhi Yong Wu 2012-10-10 10:07 ` [RFC v3 13/13] vfs: add documentation zwu.kernel 2012-10-15 0:35 ` Zheng Liu 2012-10-15 7:04 ` Zhi Yong Wu 2012-10-15 0:39 ` [RFC v3 00/13] vfs: hot data tracking Zheng Liu 2012-10-15 7:05 ` Zhi Yong Wu 2012-10-15 20:42 ` Dave Chinner 2012-10-17 8:57 ` Zhi Yong Wu 2012-10-18 4:29 ` Dave Chinner 2012-10-18 4:44 ` Zhi Yong Wu 2012-10-18 5:17 ` Dave Chinner 2012-10-18 5:24 ` Zhi Yong Wu 2012-10-19 8:29 ` Zhi Yong Wu 2012-10-16 0:04 ` [PATCH] xfs: add hot tracking support Dave Chinner 2012-11-07 8:38 ` Zhi Yong Wu 2012-11-08 5:13 ` Dave Chinner 2012-10-16 0:11 ` [RFC v3 00/13] vfs: hot data tracking Dave Chinner
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='CAEH94LgG+F2B=uw4tT1nYrZuq1ot3Sy19JjvSekZbUu4V=oOdA@mail.gmail.com' \ --to=zwu.kernel@gmail.com \ --cc=cmm@us.ibm.com \ --cc=dave@jikos.cz \ --cc=david@fromorbit.com \ --cc=lczerner@redhat.com \ --cc=linux-btrfs@vger.kernel.org \ --cc=linux-ext4@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxram@linux.vnet.ibm.com \ --cc=tytso@mit.edu \ --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: linkBe 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.