diff options
author | Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> | 2009-11-06 01:00:48 +0900 |
---|---|---|
committer | Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> | 2009-11-20 10:05:47 +0900 |
commit | 9cb4e0d2b99e8b0e5e269d898ae6ab1967647c5a (patch) | |
tree | 09ac1daa4985b4717afc818f89cfe2439664b44a /fs/libfs.c | |
parent | 09bf4aae0a3c471b721c43e7bdb6132200d907b2 (diff) | |
download | linux-9cb4e0d2b99e8b0e5e269d898ae6ab1967647c5a.tar.gz linux-9cb4e0d2b99e8b0e5e269d898ae6ab1967647c5a.tar.bz2 linux-9cb4e0d2b99e8b0e5e269d898ae6ab1967647c5a.zip |
nilfs2: move out mark_inode_dirty calls from bmap routines
Previously, nilfs_bmap_add_blocks() and nilfs_bmap_sub_blocks() called
mark_inode_dirty() after they changed the number of data blocks.
This moves these calls outside bmap outermost functions like
nilfs_bmap_insert() or nilfs_bmap_truncate().
This will mitigate overhead for truncate or delete operation since
they repeatedly remove set of blocks. Nearly 10 percent improvement
was observed for removal of a large file:
# dd if=/dev/zero of=/test/aaa bs=1M count=512
# time rm /test/aaa
real 2.968s -> 2.705s
Further optimization may be possible by eliminating these
mark_inode_dirty() uses though I avoid mixing separate changes here.
Signed-off-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Diffstat (limited to 'fs/libfs.c')
0 files changed, 0 insertions, 0 deletions