summaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems
diff options
context:
space:
mode:
authorChao Yu <chao2.yu@samsung.com>2015-02-11 11:20:38 +0100
committerJaegeuk Kim <jaegeuk@kernel.org>2015-02-12 02:04:51 +0100
commit1a118ccfd60fc78e64c0a3ab9e85075545839d6e (patch)
treee0cbaa9c068a063c71923a9b3a2c5d6168c70a6d /Documentation/filesystems
parentf2fs: fix accessing wrong indexed data blocks (diff)
downloadlinux-1a118ccfd60fc78e64c0a3ab9e85075545839d6e.tar.xz
linux-1a118ccfd60fc78e64c0a3ab9e85075545839d6e.zip
f2fs: use spinlock for segmap_lock instead of rwlock
rwlock can provide better concurrency when there are much more readers than writers because readers can hold the rwlock simultaneously. But now, for segmap_lock rwlock in struct free_segmap_info, there is only one reader 'mount' from below call path: ->f2fs_fill_super ->build_segment_manager ->build_dirty_segmap ->init_dirty_segmap ->find_next_inuse read_lock ... read_unlock Now that our concurrency can not be improved since there is no other reader for this lock, we do not need to use rwlock_t type for segmap_lock, let's replace it with spinlock_t type. Signed-off-by: Chao Yu <chao2.yu@samsung.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'Documentation/filesystems')
0 files changed, 0 insertions, 0 deletions