Jaegeuk Kim c5cd29d21c f2fs: no need to lock for update_inode_page all the time ... As comment says, we don't need to call f2fs_lock_op in write_inode to prevent from producing dirty node pages all the time. That happens only when there is not enough free sections and we can avoid that by calling balance_fs in prior to that. Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>		2015-10-09 16:20:50 -07:00
..
acl.c
acl.h
checkpoint.c
crypto_fname.c
crypto_key.c
crypto_policy.c
crypto.c
data.c
debug.c
dir.c
extent_cache.c	f2fs: trace in batches extent info update	2015-10-09 16:20:49 -07:00
f2fs_crypto.h
f2fs.h
file.c	f2fs: fix incorrect return statement in the function f2fs_ioc_release_volatile_write	2015-10-09 16:20:49 -07:00
gc.c
gc.h
hash.c
inline.c
inode.c	f2fs: no need to lock for update_inode_page all the time	2015-10-09 16:20:50 -07:00
Kconfig
Makefile
namei.c
node.c	f2fs: cover number of dirty node pages under node_write lock	2015-10-09 16:20:49 -07:00
node.h
recovery.c
segment.c
segment.h
shrinker.c
super.c
trace.c
trace.h
xattr.c
xattr.h