diff options
| author | Chao Yu <chao@kernel.org> | 2024-11-22 14:50:05 +0800 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2024-11-23 15:48:13 +0000 |
| commit | 009a8241a8e5a14ea2dd0b8db42dbf283527dd44 (patch) | |
| tree | 74ffd700984a566afdad9a80b1666cc3031e845b /rust/helpers/build_bug.c | |
| parent | 3fc5d5a182f6a1f8bd4dc775feb54c369dd2c343 (diff) | |
| download | linux-009a8241a8e5a14ea2dd0b8db42dbf283527dd44.tar.gz linux-009a8241a8e5a14ea2dd0b8db42dbf283527dd44.tar.bz2 linux-009a8241a8e5a14ea2dd0b8db42dbf283527dd44.zip | |
f2fs: add a sysfs node to limit max read extent count per-inode
Quoted:
"at this time, there are still 1086911 extent nodes in this zombie
extent tree that need to be cleaned up.
crash_arm64_sprd_v8.0.3++> extent_tree.node_cnt ffffff80896cc500
node_cnt = {
counter = 1086911
},
"
As reported by Xiuhong, there will be a huge number of extent nodes
in extent tree, it may potentially cause:
- slab memory fragments
- extreme long time shrink on extent tree
- low mapping efficiency
Let's add a sysfs node to limit max read extent count for each inode,
by default, value of this threshold is 10240, it can be updated
according to user's requirement.
Reported-by: Xiuhong Wang <xiuhong.wang@unisoc.com>
Closes: https://lore.kernel.org/linux-f2fs-devel/20241112110627.1314632-1-xiuhong.wang@unisoc.com/
Signed-off-by: Xiuhong Wang <xiuhong.wang@unisoc.com>
Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com>
Signed-off-by: Chao Yu <chao@kernel.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'rust/helpers/build_bug.c')
0 files changed, 0 insertions, 0 deletions