From: Huan Yang <link@vivo.com>
To: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeelb@google.com>,
Muchun Song <muchun.song@linux.dev>, Yu Zhao <yuzhao@google.com>,
Peter Xu <peterx@redhat.com>,
David Hildenbrand <david@redhat.com>,
"T.J. Alumbaugh" <talumbau@google.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Suren Baghdasaryan <surenb@google.com>,
linux-doc@vger.kernel.org (open list:DOCUMENTATION),
linux-kernel@vger.kernel.org (open list),
linux-mm@kvack.org (open list:MEMORY MANAGEMENT),
cgroups@vger.kernel.org (open list:CONTROL GROUP - MEMORY
RESOURCE CONTROLLER (MEMCG))
Cc: opensource.kernel@vivo.com, Huan Yang <link@vivo.com>
Subject: [PATCH 3/3] mm: multi-gen LRU: add per memcg "lru_gen" document
Date: Mon, 9 Oct 2023 10:57:22 +0800 [thread overview]
Message-ID: <20231009025726.5982-4-link@vivo.com> (raw)
In-Reply-To: <20231009025726.5982-1-link@vivo.com>
From: HuanYang <link@vivo.com>
change multi-gen LRU document.
Signed-off-by: Huan Yang <link@vivo.com>
---
Documentation/admin-guide/mm/multigen_lru.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/admin-guide/mm/multigen_lru.rst b/Documentation/admin-guide/mm/multigen_lru.rst
index 33e068830497..078056b8cc7c 100644
--- a/Documentation/admin-guide/mm/multigen_lru.rst
+++ b/Documentation/admin-guide/mm/multigen_lru.rst
@@ -160,3 +160,13 @@ cold pages because of the overestimation, it retries on the next
server according to the ranking result obtained from the working set
estimation step. This less forceful approach limits the impacts on the
existing jobs.
+
+Per memcg lru gen node
+-----------------
+In each memcg's dir, it contains ``lru_gen`` node. you can type upon cmd
+without input memcg_id to do the same thing.
+
+ ``+ node_id max_gen_nr [can_swap [force_scan]]``
+ ``- node_id min_gen_nr [swappiness [nr_to_reclaim]]``
+
+For show info, memcg's node always show the full info.
--
2.34.1
next prev parent reply other threads:[~2023-10-09 2:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 2:57 [PATCH 0/3 RESEND] Per memcg lru_gen node stat Huan Yang
2023-10-09 2:57 ` [PATCH 1/3] mm: multi-gen LRU: fold lru_gen run cmd Huan Yang
2023-10-09 2:57 ` [PATCH 2/3] mm: memcg: add per memcg "lru_gen" node Huan Yang
2023-10-09 2:57 ` Huan Yang [this message]
2023-10-18 16:33 ` [PATCH 0/3 RESEND] Per memcg lru_gen node stat Yu Zhao
2023-10-18 19:59 ` T.J. Mercier
2023-10-19 2:32 ` Huan Yang
2023-10-19 16:01 ` T.J. Mercier
2023-10-20 1:57 ` Huan Yang
-- strict thread matches above, loose matches on Subject: below --
2023-09-14 10:47 [PATCH 0/3] " Huan Yang
2023-09-14 10:47 ` [PATCH 3/3] mm: multi-gen LRU: add per memcg "lru_gen" document Huan Yang
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=20231009025726.5982-4-link@vivo.com \
--to=link@vivo.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=opensource.kernel@vivo.com \
--cc=peterx@redhat.com \
--cc=roman.gushchin@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=shakeelb@google.com \
--cc=surenb@google.com \
--cc=talumbau@google.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yuzhao@google.com \
/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
all inboxes | Powered by JetHome®