diff options
author | Denys Vlasenko <[email protected]> | 2014-06-04 16:11:03 -0700 |
---|---|---|
committer | Linus Torvalds <[email protected]> | 2014-06-04 16:54:13 -0700 |
commit | 4a0da71b96b9d4080c0820e9e7d02470ebe62dc6 (patch) | |
tree | d5fd8eb6b6f5d8877a5f84ddffa7f3e6a33e8284 /fs/jbd2/commit.c | |
parent | 3ba08129e38437561df44c36b7ea9081185d5333 (diff) |
Documentation/sysctl/vm.txt: clarify vfs_cache_pressure description
Existing description is worded in a way which almost encourages setting of
vfs_cache_pressure above 100, possibly way above it.
Users are left in a dark what this numeric value is - an int? a
percentage? what the scale is?
As a result, we are getting reports about noticeable performance
degradation from users who have set vfs_cache_pressure to ridiculously
high values - because they thought there is no downside to it.
Via code inspection it's obvious that this value is treated as a
percentage. This patch changes text to reflect this fact, and adds a
cautionary paragraph advising against setting vfs_cache_pressure sky high.
Signed-off-by: Denys Vlasenko <[email protected]>
Cc: Alexander Viro <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions