Bug 205203 - ram_thresh default (DEF_RAM_THRESHOLD) is wrong (outdated) in f2fs document
Summary: ram_thresh default (DEF_RAM_THRESHOLD) is wrong (outdated) in f2fs document
Status: RESOLVED CODE_FIX
Alias: None
Product: File System
Classification: Unclassified
Component: f2fs (show other bugs)
Hardware: All Linux
: P1 low
Assignee: Default virtual assignee for f2fs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-15 18:25 UTC by YF (Yang)
Modified: 2019-12-26 01:37 UTC (History)
1 user (show)

See Also:
Kernel Version: all
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description YF (Yang) 2019-10-15 18:25:36 UTC 
The default value appears to have been corrected by "f2fs: fix wrong percentage" commit[1], but still the old values ​​in the f2fs document[2].


ref:
1: https://github.com/torvalds/linux/commit/29710bcf9426c84bb6a9b1d94316895ed6143813
2: https://www.kernel.org/doc/Documentation/filesystems/f2fs.txt

introduces ram_thresh: https://lore.kernel.org/patchwork/patch/450476/

define DEF_RAM_THRESHOLD	1: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-stable.git/tree/fs/f2fs/node.h?h=linux-4.19.y#n23
Comment 1 Chao Yu 2019-10-22 09:29:22 UTC 
Thanks for the report, I've sent a patch for this issue.

https://lore.kernel.org/linux-f2fs-devel/20191022092611.58191-1-yuchao0@huawei.com/T/#u
Note You need to log in before you can comment on or make changes to this bug.