• Daeho Jeong's avatar
    f2fs: change the current atomic write way · 3db1de0e
    Daeho Jeong authored
    Current atomic write has three major issues like below.
     - keeps the updates in non-reclaimable memory space and they are even
       hard to be migrated, which is not good for contiguous memory
       allocation.
     - disk spaces used for atomic files cannot be garbage collected, so
       this makes it difficult for the filesystem to be defragmented.
     - If atomic write operations hit the threshold of either memory usage
       or garbage collection failure count, All the atomic write operations
       will fail immediately.
    
    To resolve the issues, I will keep a COW inode internally for all the
    updates to be flushed from memory, when we need to flush them out in a
    situation like high memory pressure. These COW inodes will be tagged
    as orphan inodes to be reclaimed in case of sudden power-cut or system
    failure during atomic writes.
    Signed-off-by: default avatarDaeho Jeong <daehojeong@google.com>
    Signed-off-by: default avatarJaegeuk Kim <jaegeuk@kernel.org>
    3db1de0e
segment.h 28.6 KB