Searched hist:"430 f163b01888dc26696365d9c1053ba9d6c7d92" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/fs/f2fs/ |
| H A D | recovery.c | diff 430f163b01888dc26696365d9c1053ba9d6c7d92 Thu Feb 03 18:34:10 CST 2022 Chao Yu <chao@kernel.org> 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>
|
| H A D | checkpoint.c | diff 430f163b01888dc26696365d9c1053ba9d6c7d92 Thu Feb 03 18:34:10 CST 2022 Chao Yu <chao@kernel.org> 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>
|
| H A D | f2fs.h | diff 430f163b01888dc26696365d9c1053ba9d6c7d92 Thu Feb 03 18:34:10 CST 2022 Chao Yu <chao@kernel.org> 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>
|