From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Jinjiang Tu <tujinjiang@huawei.com>
Cc: akpm@linux-foundation.org, david@kernel.org, xu.xin16@zte.com.cn,
chengming.zhou@linux.dev, liam@infradead.org, vbabka@kernel.org,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
corbet@lwn.net, skhan@linuxfoundation.org, shr@devkernel.io,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
wangkefeng.wang@huawei.com, sunnanyong@huawei.com
Subject: Re: [PATCH 1/2] docs: ksm: fix typos in sysfs knob names
Date: Mon, 3 Aug 2026 08:32:40 +0100 [thread overview]
Message-ID: <anBD-_khxIX-FzW-@lucifer> (raw)
In-Reply-To: <20260731083526.3953421-2-tujinjiang@huawei.com>
On Fri, Jul 31, 2026 at 04:35:25PM +0800, Jinjiang Tu wrote:
> The sysfs knob names in mm/ksm.c are "advisor_max_cpu" and
> "advisor_max_pages_to_scan", but the ksm.rst documentation spelled
> both as "adivsor_*", fix the two typos.
>
> Fixes: 0710f38ad26a ("mm/ksm: document ksm advisor and its sysfs knobs")
Same comment as David :)
> Signed-off-by: Jinjiang Tu <tujinjiang@huawei.com>
Anyway LGTM, so:
Reviewed-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> ---
> Documentation/admin-guide/mm/ksm.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/mm/ksm.rst b/Documentation/admin-guide/mm/ksm.rst
> index ad8e7a41f3b5..c9f533b10f6f 100644
> --- a/Documentation/admin-guide/mm/ksm.rst
> +++ b/Documentation/admin-guide/mm/ksm.rst
> @@ -174,7 +174,7 @@ advisor_mode
> The section about ``advisor`` explains in detail how the scan time
> advisor works.
>
> -adivsor_max_cpu
> +advisor_max_cpu
> specifies the upper limit of the cpu percent usage of the ksmd
> background thread. The default is 70.
>
> @@ -186,7 +186,7 @@ advisor_min_pages_to_scan
> specifies the lower limit of the ``pages_to_scan`` parameter of the
> scan time advisor. The default is 500.
>
> -adivsor_max_pages_to_scan
> +advisor_max_pages_to_scan
> specifies the upper limit of the ``pages_to_scan`` parameter of the
> scan time advisor. The default is 30000.
>
> --
> 2.54.0
>
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-08-03 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 8:35 [PATCH 0/2] docs/ksm: fix advisor documentation and comment Jinjiang Tu
2026-07-31 8:35 ` [PATCH 1/2] docs: ksm: fix typos in sysfs knob names Jinjiang Tu
2026-07-31 9:11 ` David Hildenbrand (Arm)
2026-07-31 9:22 ` Jinjiang Tu
2026-07-31 9:25 ` David Hildenbrand (Arm)
2026-08-03 7:15 ` Jinjiang Tu
2026-08-03 7:54 ` David Hildenbrand (Arm)
2026-08-04 2:15 ` Jinjiang Tu
2026-08-03 7:32 ` Lorenzo Stoakes (ARM) [this message]
2026-07-31 8:35 ` [PATCH 2/2] mm/ksm: fix advisor_min_pages_to_scan description Jinjiang Tu
[not found] ` <33b55954-71e7-4e8d-868a-0440c1b28ae8@kernel.org>
2026-07-31 9:24 ` Jinjiang Tu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=anBD-_khxIX-FzW-@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=shr@devkernel.io \
--cc=skhan@linuxfoundation.org \
--cc=sunnanyong@huawei.com \
--cc=surenb@google.com \
--cc=tujinjiang@huawei.com \
--cc=vbabka@kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=xu.xin16@zte.com.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox