f2fs: recover wrong pino after checkpoint during fsync

If a file is linked, f2fs loose its parent inode number so that fsync calls
for the linked file should do checkpoint all the time.
But, if we can recover its parent inode number after the checkpoint, we can
adjust roll-forward mechanism for the further fsync calls, which is able to
improve the fsync performance significatly.

Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>

1 files changed, 11 insertions, 4 deletions

diff --git a/fs/f2fs/node.h b/fs/f2fs/node.h
index a503661307db..c65fb4f4230f 100644
--- a/fs/f2fs/node.h
+++ b/fs/f2fs/node.h
@@ -285,10 +285,17 @@ static inline void set_file(struct inode *inode, int type)
         F2FS_I(inode)->i_advise |= type;
 }
 
-#define is_cold_file(inode)     is_file(inode, FADVISE_COLD_BIT)
-#define is_cp_file(inode)       is_file(inode, FADVISE_CP_BIT)
-#define set_cold_file(inode)    set_file(inode, FADVISE_COLD_BIT)
-#define set_cp_file(inode)      set_file(inode, FADVISE_CP_BIT)
+static inline void clear_file(struct inode *inode, int type)
+{
+        F2FS_I(inode)->i_advise &= ~type;
+}
+
+#define file_is_cold(inode)     is_file(inode, FADVISE_COLD_BIT)
+#define file_wrong_pino(inode)  is_file(inode, FADVISE_LOST_PINO_BIT)
+#define file_set_cold(inode)    set_file(inode, FADVISE_COLD_BIT)
+#define file_lost_pino(inode)   set_file(inode, FADVISE_LOST_PINO_BIT)
+#define file_clear_cold(inode)  clear_file(inode, FADVISE_COLD_BIT)
+#define file_got_pino(inode)    clear_file(inode, FADVISE_LOST_PINO_BIT)
 
 static inline int is_cold_data(struct page *page)
 {