From: Lance Yang <ioworker0@gmail.com>
To: akpm@linux-foundation.org
Cc: ioworker0@gmail.com, 21cnbao@gmail.com, baohua@kernel.org,
baolin.wang@linux.alibaba.com, david@redhat.com,
dj456119@gmail.com, libang.li@antgroup.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mingzhe.yang@ly.com, ryan.roberts@arm.com, shy828301@gmail.com,
ziy@nvidia.com
Subject: Re: [PATCH v3 2/2] mm: add docs for per-order mTHP split counters
Date: Sun, 7 Jul 2024 09:36:59 +0800 [thread overview]
Message-ID: <20240707013659.1151-1-ioworker0@gmail.com> (raw)
In-Reply-To: <20240704012905.42971-3-ioworker0@gmail.com>
Hi Andrew,
Could you please fold the following changes into this patch?
diff --git a/Documentation/admin-guide/mm/transhuge.rst b/Documentation/admin-guide/mm/transhuge.rst
index 747c811ee8f1..fe237825b95c 100644
--- a/Documentation/admin-guide/mm/transhuge.rst
+++ b/Documentation/admin-guide/mm/transhuge.rst
@@ -513,17 +513,16 @@ split
is incremented every time a huge page is successfully split into
smaller orders. This can happen for a variety of reasons but a
common reason is that a huge page is old and is being reclaimed.
- This action implies splitting any block mappings into PTEs.
split_failed
is incremented if kernel fails to split huge
page. This can happen if the page was pinned by somebody.
split_deferred
- is incremented when a huge page is put onto split
- queue. This happens when a huge page is partially unmapped and
- splitting it would free up some memory. Pages on split queue are
- going to be split under memory pressure.
+ is incremented when a huge page is put onto split queue.
+ This happens when a huge page is partially unmapped and splitting
+ it would free up some memory. Pages on split queue are going to
+ be split under memory pressure, if splitting is possible.
As the system ages, allocating huge pages may be expensive as the
system uses memory compaction to copy data around memory to free a
--
Thanks,
Lance
prev parent reply other threads:[~2024-07-07 1:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 1:29 [PATCH v3 0/2] mm: introduce " Lance Yang
2024-07-04 1:29 ` [PATCH v3 1/2] mm: add " Lance Yang
2024-07-05 9:08 ` David Hildenbrand
2024-07-05 10:12 ` Barry Song
2024-07-05 10:14 ` David Hildenbrand
2024-07-05 10:48 ` Lance Yang
2024-07-05 10:55 ` David Hildenbrand
2024-07-05 11:19 ` Lance Yang
2024-07-05 11:31 ` Lance Yang
2024-07-04 1:29 ` [PATCH v3 2/2] mm: add docs for " Lance Yang
2024-07-05 9:09 ` David Hildenbrand
2024-07-05 9:16 ` Ryan Roberts
2024-07-05 9:25 ` David Hildenbrand
2024-07-05 11:08 ` Lance Yang
2024-07-07 1:36 ` Lance Yang [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=20240707013659.1151-1-ioworker0@gmail.com \
--to=ioworker0@gmail.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dj456119@gmail.com \
--cc=libang.li@antgroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingzhe.yang@ly.com \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=ziy@nvidia.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