Btrfs: use signed integer instead of unsigned long integer for log transid

The log trans id is initialized to be 0 every time we create a log tree,
and the log tree need be re-created after a new transaction is started,
it means the log trans id is unlikely to be a huge number, so we can use
signed integer instead of unsigned long integer to save a bit space.

Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Signed-off-by: Josef Bacik <jbacik@fb.com>

1 files changed, 7 insertions, 7 deletions

diff --git a/fs/btrfs/btrfs_inode.h b/fs/btrfs/btrfs_inode.h
index 8fed2125689e..c9a24444ec9a 100644
--- a/fs/btrfs/btrfs_inode.h
+++ b/fs/btrfs/btrfs_inode.h
@@ -109,14 +109,17 @@ struct btrfs_inode {
         u64 last_trans;
 
         /*
-         * log transid when this inode was last modified
+         * transid that last logged this inode
          */
-        u64 last_sub_trans;
+        u64 logged_trans;
 
         /*
-         * transid that last logged this inode
+         * log transid when this inode was last modified
          */
-        u64 logged_trans;
+        int last_sub_trans;
+
+        /* a local copy of root's last_log_commit */
+        int last_log_commit;
 
         /* total number of bytes pending delalloc, used by stat to calc the
          * real block usage of the file
@@ -155,9 +158,6 @@ struct btrfs_inode {
         /* flags field from the on disk inode */
         u32 flags;
 
-        /* a local copy of root's last_log_commit */
-        unsigned long last_log_commit;
-
         /*
          * Counters to keep track of the number of extent item's we may use due
          * to delalloc and such.  outstanding_extents is the number of extent