linux.git/fs/f2fs/segment.c, branch v3.19

f2fs: count the number of inmemory pages

2014-12-08T18:35:15+00:00

This patch adds counting # of inmemory pages in the page cache.

Signed-off-by: Jaegeuk Kim

f2fs: set page private for inmemory pages for truncation

2014-12-08T18:35:14+00:00

The inmemory pages should be handled by invalidate_page since it needs to be
released int the truncation path.

Signed-off-by: Jaegeuk Kim

f2fs: do retry operations with cond_resched

2014-12-08T18:35:05+00:00

This patch revists retrial paths in f2fs.
The basic idea is to use cond_resched instead of retrying from the very early
stage.

Suggested-by: Gu Zheng 
Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: fix livelock calling f2fs_iget during f2fs_evict_inode

2014-11-24T05:51:57+00:00

In f2fs_evict_inode,
 commit_inmemory_pages
   f2fs_gc
     f2fs_iget
       iget_locked
         -> wait for inode free

Here, if the inode is same as the one to be evicted, f2fs should wait forever.
Actually, we should not call f2fs_balance_fs during f2fs_evict_inode to avoid
this.

But, the commit_inmem_pages calls f2fs_balance_fs by default, even if
f2fs_evict_inode wants to free inmemory pages only.

Hence, this patch adds to trigger f2fs_balance_fs only when there is something
to write.

Signed-off-by: Jaegeuk Kim

f2fs: fix wrong data structure when create slab

2014-11-24T05:48:49+00:00

It used nat_entry_set when create slab for sit_entry_set.

Signed-off-by: Changman Lee 
Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: control the memory footprint used by ino entries

2014-11-06T23:24:46+00:00

This patch adds to control the memory footprint used by ino entries.
This will conduct best effort, not strictly.

Signed-off-by: Jaegeuk Kim

f2fs: disable roll-forward when active_logs = 2

2014-11-06T04:05:53+00:00

The roll-forward mechanism should be activated when the number of active
logs is not 2.

Signed-off-by: Jaegeuk Kim

f2fs: send discard commands in larger extent

2014-11-05T01:34:13+00:00

If there is a chance to make a huge sized discard command, we don't need
to split it out, since each blkdev_issue_discard should wait one at a
time.

Signed-off-by: Jaegeuk Kim

f2fs: do not discard data protected by the previous checkpoint

2014-11-04T00:07:38+00:00

We should not discard any data protected by the previous checkpoint all
the time.

Signed-off-by: Jaegeuk Kim

f2fs: call write_checkpoint under disabled gc

2014-11-04T00:07:37+00:00

During the write_checkpoint, we should avoid f2fs_gc trigger to avoid any
filesystem consistency.

Signed-off-by: Jaegeuk Kim