aboutsummaryrefslogtreecommitdiffstats
path: root/fs/f2fs/f2fs.h
diff options
context:
space:
mode:
authorJaegeuk Kim <jaegeuk.kim@samsung.com>2013-06-13 19:52:35 -0400
committerJaegeuk Kim <jaegeuk.kim@samsung.com>2013-06-13 20:04:45 -0400
commit354a3399dc6f7e556d04e1c731cd50e08eeb44bd (patch)
tree755e9c85c22dd0aa8dfdfc204e5697afd99b67af /fs/f2fs/f2fs.h
parentb25958b6ecf1dce087e62b9aa27cf8f2fe9b5c86 (diff)
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>
Diffstat (limited to 'fs/f2fs/f2fs.h')
-rw-r--r--fs/f2fs/f2fs.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 3e7cb33b64d3..863a5e91d84a 100644
--- a/fs/f2fs/f2fs.h
+++ b/fs/f2fs/f2fs.h
@@ -151,7 +151,7 @@ struct extent_info {
151 * i_advise uses FADVISE_XXX_BIT. We can add additional hints later. 151 * i_advise uses FADVISE_XXX_BIT. We can add additional hints later.
152 */ 152 */
153#define FADVISE_COLD_BIT 0x01 153#define FADVISE_COLD_BIT 0x01
154#define FADVISE_CP_BIT 0x02 154#define FADVISE_LOST_PINO_BIT 0x02
155 155
156struct f2fs_inode_info { 156struct f2fs_inode_info {
157 struct inode vfs_inode; /* serve a vfs inode */ 157 struct inode vfs_inode; /* serve a vfs inode */