linux-stable.git/fs/f2fs/node.h, branch v4.17

f2fs: don't track new nat entry in nat set

2018-03-28T03:10:29+00:00

Nat entry set is used only in checkpoint(), and during checkpoint() we
won't flush new nat entry with unallocated address, so we don't need to
add new nat entry into nat set, then nat_entry_set::entry_cnt can
indicate actual entry count we need to flush in checkpoint().

Signed-off-by: Yunlei He 
Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: remove unneeded set_cold_node()

2018-03-17T04:57:33+00:00

When setting COLD_BIT_SHIFT flag in node block, we only need to call
set_cold_node() in new_node_page() and recover_inode_page() during
node page initialization. So remove unneeded set_cold_node() in other
places.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: allow to recover node blocks given updated checkpoint

2018-01-22T22:56:59+00:00

If fsck.f2fs changes crc, we have no way to recover some inode blocks by roll-
forward recovery. Let's relax the condition to recover them.

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

f2fs: limit # of inmemory pages

2017-10-26T08:44:21+00:00

If some abnormal users try lots of atomic write operations, f2fs is able to
produce pinned pages in the main memory which affects system performance.
This patch limits that as 20% over total memory size, and if f2fs reaches
to the limit, it will drop all the inmemory pages.

Signed-off-by: Jaegeuk Kim

f2fs: obsolete ALLOC_NID_LIST list

2017-10-10T19:49:53+00:00

As Fan Li reported, there is no user traversing nid_list[ALLOC_NID_LIST]
which is used for tracking preallocated nids. Let's drop it, and only
track preallocated nids in free_nid_root radix-tree.

Reported-by: Fan Li 
Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: simplify the way of calulating next nat address

2017-07-04T09:11:34+00:00

The index of segment which the next nat block is in has only one different
bit than the current one, so to get the next nat address, we can simply
alter that one bit.

Signed-off-by: Fan Li 
Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: guard macro variables with braces

2017-04-11T02:48:10+00:00

Add braces around variables used within macros for those make sense
to do it. Many of the macros in f2fs already do this. What this commit
doesn't do is anything that changes line# as a result of adding braces,
which usually affects the binary via __LINE__.

Confirmed no diff in fs/f2fs/f2fs.ko before/after this commit on x86_64,
to make sure this has no functional change as well as there's been no
unexpected side effect due to callers' arithmetics within the existing
code.

Signed-off-by: Tomohiro Kusumi 
Signed-off-by: Jaegeuk Kim

f2fs: adjust the way of calculating nat block

2017-03-22T02:34:27+00:00

use a slightly simpler expression to calculate nat block with nid.

Signed-off-by: Fan Li 
Signed-off-by: Jaegeuk Kim

f2fs: new helper cur_cp_crc() getting crc in f2fs_checkpoint

2017-02-27T18:07:47+00:00

There are four places that getting the crc value in f2fs_checkpoint,
just add a new helper cur_cp_crc for them.

Signed-off-by: Kinglong Mee 
Signed-off-by: Jaegeuk Kim

f2fs: remove unsafe bitmap checking

2017-02-27T17:59:51+00:00

proc A:                      proc B:
- writeback_sb_inodes
- __writeback_single_inode
- do_writepages
- f2fs_write_node_pages
- f2fs_balance_fs_bg         - write_checkpoint
- build_free_nids            - flush_nat_entries
- __build_free_nids          - __flush_nat_entry_set
- ra_meta_pages              - get_next_nat_page
- current_nat_addr           - set_to_next_nat
[do nat_bitmap checking]     - f2fs_change_bit

For proc A, nat_bitmap and nat_bitmap_mir would be compared without lock_op and
nm_i->nat_tree_lock, while proc B is changing nat_bitmap/nat_bitmap_ver in cp.

So it is normal for nat_bitmap/nat_bitmap diffrence under such scenario.

This patch fix this by removing the monitoring point.

[Fix: 599a09b f2fs: check in-memory nat version bitmap]
Signed-off-by: Hou Pengyang 
Signed-off-by: Jaegeuk Kim