diff options
| author | Chao Yu <chao@kernel.org> | 2022-02-04 03:34:10 +0300 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2022-02-04 09:21:28 +0300 |
| commit | 430f163b01888dc26696365d9c1053ba9d6c7d92 (patch) | |
| tree | 076333f82610ab1c0ea54be69b4a12cb23009e58 /fs/f2fs/data.c | |
| parent | 6d18762ed5cd549fde74fd0e05d4d87bac5a3beb (diff) | |
| download | linux-430f163b01888dc26696365d9c1053ba9d6c7d92.tar.xz | |
f2fs: adjust readahead block number during recovery
In a fragmented image, entries in dnode block list may locate in
incontiguous physical block address space, however, in recovery flow,
we will always readahead BIO_MAX_VECS size blocks, so in such case,
current readahead policy is low efficient, let's adjust readahead
window size dynamically based on consecutiveness of dnode blocks.
Signed-off-by: Chao Yu <chao@kernel.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/data.c')
0 files changed, 0 insertions, 0 deletions