linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Barry Song <21cnbao@gmail.com>
To: david@redhat.com, akpm@linux-foundation.org, linux-mm@kvack.org,
	ryan.roberts@arm.com
Cc: cerasuolodomenico@gmail.com, chrisl@kernel.org,
	kasong@tencent.com, peterx@redhat.com, surenb@google.com,
	v-songbaohua@oppo.com, willy@infradead.org,
	yosryahmed@google.com, yuzhao@google.com,
	linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/2] mm: add per-order mTHP alloc and swpout counters
Date: Fri,  5 Apr 2024 23:27:02 +1300	[thread overview]
Message-ID: <20240405102704.77559-1-21cnbao@gmail.com> (raw)

From: Barry Song <v-songbaohua@oppo.com>

The patchset introduces a framework to facilitate mTHP counters, starting
with the allocation and swap-out counters. Currently, only four new nodes
are appended to the stats directory for each mTHP size.

/sys/kernel/mm/transparent_hugepage/hugepages-<size>/stats
	anon_alloc
	anon_alloc_fallback
	anon_swpout
	anon_swpout_fallback

These four nodes are crucial for us to monitor the fragmentation levels of
both the buddy system and the swapfile. In the future, we may consider
adding additional nodes for further insights.

-v4:
  * Many thanks to David and Ryan for your patience and valuable insights
    throughout the numerous renaming efforts!
  * Guard the case order > PMD_ORDER in count func rather than in callers,
    Ryan;
  * Add swpout counters;
  * Add a helper DEFINE_MTHP_STAT_ATTR to avoid code duplication for various
    counters;

-v3:
  https://lore.kernel.org/linux-mm/20240403035502.71356-1-21cnbao@gmail.com/

Barry Song (2):
  mm: add per-order mTHP anon_alloc and anon_alloc_fallback counters
  mm: add per-order mTHP anon_swpout and anon_swpout_fallback counters

 include/linux/huge_mm.h | 21 +++++++++++++++++
 mm/huge_memory.c        | 52 +++++++++++++++++++++++++++++++++++++++++
 mm/memory.c             |  2 ++
 mm/page_io.c            |  6 ++++-
 mm/vmscan.c             |  3 +++
 5 files changed, 83 insertions(+), 1 deletion(-)

-- 
2.34.1



             reply	other threads:[~2024-04-05 10:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 10:27 Barry Song [this message]
2024-04-05 10:27 ` [PATCH v4 1/2] mm: add per-order mTHP anon_alloc and anon_alloc_fallback counters Barry Song
2024-04-11 16:38   ` Ryan Roberts
2024-04-11 22:40     ` Barry Song
2024-04-12  9:16       ` Ryan Roberts
2024-04-12  9:27         ` Barry Song
2024-04-05 10:27 ` [PATCH v4 2/2] mm: add per-order mTHP anon_swpout and anon_swpout_fallback counters Barry Song
2024-04-11 16:43   ` Ryan Roberts
2024-04-11 21:52     ` Barry Song
2024-04-05 20:11 ` [PATCH v4 0/2] mm: add per-order mTHP alloc and swpout counters Andrew Morton
2024-04-05 22:04   ` Barry Song
2024-04-11 16:45     ` 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=20240405102704.77559-1-21cnbao@gmail.com \
    --to=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cerasuolodomenico@gmail.com \
    --cc=chrisl@kernel.org \
    --cc=david@redhat.com \
    --cc=kasong@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=surenb@google.com \
    --cc=v-songbaohua@oppo.com \
    --cc=willy@infradead.org \
    --cc=yosryahmed@google.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;
as well as URLs for NNTP newsgroup(s).