f2fs: kill f2fs_drop_largest_extent

Browse source

For direct IO, f2fs only allocate new address for the block which is not
exist in the disk before, its mapping info should not exist in extent
cache previously, so here we do not need to call f2fs_drop_largest_extent
to drop related cache.

Due to no more callers for f2fs_drop_largest_extent now, kill it.

Signed-off-by: Chao Yu <chao2.yu@samsung.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

...

This commit is contained in:

Chao Yu 2015-12-01 11:47:33 +08:00 • committed by Jaegeuk Kim

parent b7973f2378

commit 9006f2c93f

3 changed files with 0 additions and 13 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

4

fs/f2fs/data.c

View file

8

fs/f2fs/extent_cache.c

View file

1

fs/f2fs/f2fs.h

View file