diff options
| author | Chao Yu <[email protected]> | 2016-08-21 23:21:30 +0800 |
|---|---|---|
| committer | Jaegeuk Kim <[email protected]> | 2016-09-07 17:27:33 -0700 |
| commit | 74fa5f3d43bca87257e9da7da95be8735ffa2b96 (patch) | |
| tree | a3d972110c11454cbf7c5964bd49184863d9f229 | |
| parent | 97c1794a5dc160164aa7f161310da15c34d62641 (diff) | |
f2fs: schedule in between two continous batch discards
In batch discard approach of fstrim will grab/release gc_mutex lock
repeatly, it makes contention of the lock becoming more intensive.
So after one batch discards were issued in checkpoint and the lock
was released, it's better to do schedule() to increase opportunity
of grabbing gc_mutex lock for other competitors.
Signed-off-by: Chao Yu <[email protected]>
Signed-off-by: Jaegeuk Kim <[email protected]>
| -rw-r--r-- | fs/f2fs/segment.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c index 020767c67935..d0f74eb521ae 100644 --- a/fs/f2fs/segment.c +++ b/fs/f2fs/segment.c @@ -1305,6 +1305,8 @@ int f2fs_trim_fs(struct f2fs_sb_info *sbi, struct fstrim_range *range) mutex_unlock(&sbi->gc_mutex); if (err) break; + + schedule(); } out: range->len = F2FS_BLK_TO_BYTES(cpc.trimmed); |