From: David Hildenbrand <david@redhat.com>
To: Stefan Roesch <shr@devkernel.io>, kernel-team@fb.com
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org, riel@surriel.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 4/4] mm/ksm: document ksm advisor and its sysfs knobs
Date: Tue, 12 Dec 2023 14:46:23 +0100 [thread overview]
Message-ID: <525a4d9c-efaf-4663-a354-10f9e3ff2148@redhat.com> (raw)
In-Reply-To: <20231204234906.1237478-5-shr@devkernel.io>
On 05.12.23 00:49, Stefan Roesch wrote:
> This documents the KSM advisor and its new knobs in /sys/fs/kernel/mm.
>
> Signed-off-by: Stefan Roesch <shr@devkernel.io>
> ---
> Documentation/admin-guide/mm/ksm.rst | 54 ++++++++++++++++++++++++++++
> 1 file changed, 54 insertions(+)
>
> diff --git a/Documentation/admin-guide/mm/ksm.rst b/Documentation/admin-guide/mm/ksm.rst
> index e59231ac6bb71..297c4a0d04dee 100644
> --- a/Documentation/admin-guide/mm/ksm.rst
> +++ b/Documentation/admin-guide/mm/ksm.rst
> @@ -80,6 +80,9 @@ pages_to_scan
> how many pages to scan before ksmd goes to sleep
> e.g. ``echo 100 > /sys/kernel/mm/ksm/pages_to_scan``.
>
> + The pages_to_scan value cannot be changed if ``advisor_mode`` has
> + been set to scan-time.
> +
> Default: 100 (chosen for demonstration purposes)
>
> sleep_millisecs
> @@ -164,6 +167,29 @@ smart_scan
> optimization is enabled. The ``pages_skipped`` metric shows how
> effective the setting is.
>
> +advisor_mode
> + The ``advisor_mode`` selects the current advisor. Two modes are
> + supported: none and scan-time. The default is none. By setting
> + ``advisor_mode`` to scan-time, the scan time advisor is enabled.
> + The section about ``advisor`` explains in detail how the scan time
> + advisor works.
> +
> +adivsor_max_cpu
> + specifies the upper limit of the cpu percent usage of the ksmd
> + background thread. The default is 70.
> +
> +advisor_target_scan_time
> + specifies the target scan time in seconds to scan all the candidate
> + pages. The default value is 200 seconds.
> +
> +advisor_min_pages
> + specifies the lower limit of the ``pages_to_scan`` parameter of the
> + scan time advisor. The default is 500.
> +
> +adivsor_max_pages
> + specifies the upper limit of the ``pages_to_scan`` parameter of the
> + scan time advisor. The default is 30000.
> +
> The effectiveness of KSM and MADV_MERGEABLE is shown in ``/sys/kernel/mm/ksm/``:
>
> general_profit
> @@ -263,6 +289,34 @@ ksm_swpin_copy
> note that KSM page might be copied when swapping in because do_swap_page()
> cannot do all the locking needed to reconstitute a cross-anon_vma KSM page.
>
> +Advisor
> +=======
> +
> +The number of candidate pages for KSM is dynamic. It can be often observed
> +that during the startup of an application more candidate pages need to be
> +processed. Without an advisor the ``pages_to_scan`` parameter needs to be
> +sized for the maximum number of candidate pages. The scan time advisor can
> +changes the ``pages_to_scan`` parameter based on demand.
> +
> +The advisor can be enabled, so KSM can automatically adapt to changes in the
> +number of candidate pages to scan. Two advisors are implemented: none and
> +scan-time. With none, no advisor is enabled. The default is none.
> +
> +The scan time advisor changes the ``pages_to_scan`` parameter based on the
> +observed scan times. The possible values for the ``pages_to_scan`` parameter is
> +limited by the ``advisor_max_cpu`` parameter. In addition there is also the
> +``advisor_target_scan_time`` parameter. This parameter sets the target time to
> +scan all the KSM candidate pages. The parameter ``advisor_target_scan_time``
> +decides how aggressive the scan time advisor scans candidate pages. Lower
> +values make the scan time advisor to scan more aggresively. This is the most
> +important parameter for the configuration of the scan time advisor.
> +
> +The initial value and the maximum value can be changed with ``advisor_min_pages``
> +and ``advisor_max_pages``. The default values are sufficient for most workloads.
> +
> +The ``pages_to_scan`` parameter is re-calculated after a scan has been completed.
Acked-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-12-12 13:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 23:49 [PATCH v3 0/4] mm/ksm: Add ksm advisor Stefan Roesch
2023-12-04 23:49 ` [PATCH v3 1/4] mm/ksm: add " Stefan Roesch
2023-12-06 15:17 ` kernel test robot
2023-12-12 13:44 ` David Hildenbrand
2023-12-12 18:32 ` Stefan Roesch
2023-12-04 23:49 ` [PATCH v3 2/4] mm/ksm: add sysfs knobs for advisor Stefan Roesch
2023-12-12 13:45 ` David Hildenbrand
2023-12-12 18:02 ` Stefan Roesch
2023-12-12 18:07 ` David Hildenbrand
2023-12-12 18:27 ` Stefan Roesch
2023-12-04 23:49 ` [PATCH v3 3/4] mm/ksm: add tracepoint for ksm advisor Stefan Roesch
2023-12-12 13:45 ` David Hildenbrand
2023-12-04 23:49 ` [PATCH v3 4/4] mm/ksm: document ksm advisor and its sysfs knobs Stefan Roesch
2023-12-12 13:46 ` David Hildenbrand [this message]
2023-12-05 20:46 ` [PATCH v3 0/4] mm/ksm: Add ksm advisor Andrew Morton
2023-12-07 23:18 ` Stefan Roesch
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=525a4d9c-efaf-4663-a354-10f9e3ff2148@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=shr@devkernel.io \
/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