From: Lance Yang <ioworker0@gmail.com>
To: akpm@linux-foundation.org
Cc: dj456119@gmail.com, 21cnbao@gmail.com, ryan.roberts@arm.com,
david@redhat.com, shy828301@gmail.com, ziy@nvidia.com,
libang.li@antgroup.com, baolin.wang@linux.alibaba.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Lance Yang <ioworker0@gmail.com>
Subject: [PATCH v2 0/2] mm: introduce per-order mTHP split counters
Date: Fri, 28 Jun 2024 21:07:48 +0800 [thread overview]
Message-ID: <20240628130750.73097-1-ioworker0@gmail.com> (raw)
Hi all,
Currently, the split counters in THP statistics no longer include
PTE-mapped mTHP. Therefore, we propose introducing per-order mTHP split
counters to monitor the frequency of mTHP splits. This will help developers
better analyze and optimize system performance.
/sys/kernel/mm/transparent_hugepage/hugepages-<size>/stats
split
split_failed
split_deferred
---
Changes since v1 [1]
====================
- mm: add per-order mTHP split counters
- Update the changelog
- Drop '_page' from mTHP split counter names (per David and Ryan)
- Store the order of the folio in a variable and reuse it later
(per Bang)
- mm: add docs for per-order mTHP split counters
- Improve the doc suggested by Ryan
[1] https://lore.kernel.org/linux-mm/20240424135148.30422-1-ioworker0@gmail.com
Lance Yang (2):
mm: add per-order mTHP split counters
mm: add docs for per-order mTHP split counters
Documentation/admin-guide/mm/transhuge.rst | 16 ++++++++++++++++
include/linux/huge_mm.h | 3 +++
mm/huge_memory.c | 19 ++++++++++++++-----
3 files changed, 33 insertions(+), 5 deletions(-)
--
2.45.2
next reply other threads:[~2024-06-28 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 13:07 Lance Yang [this message]
2024-06-28 13:07 ` [PATCH v2 1/2] mm: add " Lance Yang
2024-07-01 0:02 ` Barry Song
2024-07-01 1:42 ` Lance Yang
2024-07-01 2:23 ` Baolin Wang
2024-07-01 10:36 ` Lance Yang
2024-07-01 8:18 ` Ryan Roberts
2024-07-01 10:37 ` Lance Yang
2024-06-28 13:07 ` [PATCH v2 2/2] mm: add docs for " Lance Yang
2024-06-29 3:08 ` Barry Song
2024-06-29 14:30 ` Lance Yang
2024-07-01 8:31 ` Ryan Roberts
2024-07-01 10:50 ` Lance Yang
2024-07-01 11:46 ` Ryan Roberts
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=20240628130750.73097-1-ioworker0@gmail.com \
--to=ioworker0@gmail.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.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=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