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>
This commit is contained in:
@@ -796,7 +796,7 @@ static int __get_segment_type_6(struct page *page, enum page_type p_type)
|
||||
|
||||
if (S_ISDIR(inode->i_mode))
|
||||
return CURSEG_HOT_DATA;
|
||||
else if (is_cold_data(page) || is_cold_file(inode))
|
||||
else if (is_cold_data(page) || file_is_cold(inode))
|
||||
return CURSEG_COLD_DATA;
|
||||
else
|
||||
return CURSEG_WARM_DATA;
|
||||
|
Reference in New Issue
Block a user