zswap: docs/vm: Fix typo accept_threshold_percent in zswap.rst
PATCH 1/1 zswap: docs/vm: Fix typo accept_threshold_percent in zswap.rst
Recently, I switched over from swap-file to zramswap.
When reading the Documentation/vm/zswap.rst file I fell over this typo.
The parameter is called accept_threshold_percent not accept_threhsold_percent in /sys/module/zswap/parameters/ directory.
---
Changes v1->v2:
- Changed subject line
- Resend to LKML with correct email-address
Documentation/vm/zswap.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/vm/zswap.rst +2 -2
@@ -140,10 +140,10 @@ without any real benefit but with a performance drop for the system), a special parameter has been introduced to implement a sort of hysteresis to refuse taking pages into zswap pool until it has sufficient space if the limit has been hit. To set the threshold at which zswap would start accepting pages -again after it became full, use the sysfs ``accept_threhsold_percent`` +again after it became full, use the sysfs ``accept_threshold_percent`` attribute, e. g.:: - echo 80 > /sys/module/zswap/parameters/accept_threhsold_percent + echo 80 > /sys/module/zswap/parameters/accept_threshold_percent Setting this parameter to 100 will disable the hysteresis.
Signature · 1 line
2.27.0.rc2
Quoted 10 lines · On Mon, 1 Jun 2020 02:59:11 +0200 Sedat Dilek <[email protected]> wrote:
Recently, I switched over from swap-file to zramswap.
When reading the
Documentation/vm/zswap.rstfile I fell over this typo.The parameter is called
accept_threshold_percentnotaccept_threhsold_percentin/sys/module/zswap/parameters/directory.Fixes 45190f01dd402 ("mm/zswap.c: add allocation hysteresis if pool limit is hit")Cc Vitaly Wool <[email protected]>Signed-off-by Sedat Dilek <[email protected]>
Applied, thanks.
Quoted 3 lines
Changes
v1->v2:
- Changed subject line
- Resend to LKML with correct email-address
When you make a v2 like this, it's helpful if you mark it as "[PATCH v2]". I had three versions of this in my inbox and had to figure out what was going on...
jon