From: Jinjiang Tu <tujinjiang@huawei.com>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
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 v2 0/2] docs/ksm: fix advisor documentation and comment
Date: Mon, 17 Aug 2026 11:12:58 +0800 [thread overview]
Message-ID: <4b9293fc-82d1-4776-81d6-d7463439c1ae@huawei.com> (raw)
In-Reply-To: <an3VdkvUvLapWzmw@lucifer>
在 2026/8/13 22:35, Lorenzo Stoakes (ARM) 写道:
> This is a very bare cover letter...
I updated it:
This series fixes two problems left in the KSM advisor documentation
and code comment:
- Patch 1 fixes two typos in sysfs knob names ("adivsor_max_cpu" and
"adivsor_max_pages_to_scan") in ksm.rst that don't match the actual
knob names.
- Patch 2 fixes the description of advisor_min_pages_to_scan: it is
described as the lower limit of pages_to_scan, but is actually only
used as it's initial value, and the runtime pages_to_scan can drop
below advisor_min_pages_to_scan.
prev parent reply other threads:[~2026-08-17 3:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 3:17 [PATCH v2 0/2] docs/ksm: fix advisor documentation and comment Jinjiang Tu
2026-08-13 3:17 ` [PATCH v2 1/2] docs: ksm: fix typos in sysfs knob names Jinjiang Tu
2026-08-13 4:47 ` Randy Dunlap
2026-08-13 3:17 ` [PATCH v2 2/2] mm/ksm: fix advisor_min_pages_to_scan description Jinjiang Tu
2026-08-13 10:56 ` Lorenzo Stoakes (ARM)
2026-08-13 11:17 ` Jinjiang Tu
2026-08-13 14:32 ` Lorenzo Stoakes (ARM)
2026-08-17 2:54 ` Jinjiang Tu
2026-08-17 16:55 ` Lorenzo Stoakes (ARM)
2026-08-18 2:28 ` Jinjiang Tu
2026-08-13 14:35 ` [PATCH v2 0/2] docs/ksm: fix advisor documentation and comment Lorenzo Stoakes (ARM)
2026-08-17 3:12 ` Jinjiang Tu [this message]
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=4b9293fc-82d1-4776-81d6-d7463439c1ae@huawei.com \
--to=tujinjiang@huawei.com \
--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=ljs@kernel.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=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