From: Yin Fengwei <fengwei.yin@intel.com>
To: linux-mm@kvack.org, akpm@linux-foundation.org, jack@suse.cz,
hughd@google.com, kirill.shutemov@linux.intel.com,
mhocko@suse.com, ak@linux.intel.com, aarcange@redhat.com,
npiggin@gmail.com, mgorman@techsingularity.net,
willy@infradead.org, rppt@kernel.org, dave.hansen@intel.com,
ying.huang@intel.com, tim.c.chen@intel.com
Cc: fengwei.yin@intel.com
Subject: [RFC PATCH 3/4] mcpage: add vmstat counters for mcpages
Date: Mon, 9 Jan 2023 15:22:31 +0800 [thread overview]
Message-ID: <20230109072232.2398464-4-fengwei.yin@intel.com> (raw)
In-Reply-To: <20230109072232.2398464-1-fengwei.yin@intel.com>
MCPAGE_ANON_FAULT_ALLOC: how many times mcpage is used for anonymous
mapping.
MCPAGE_ANON_FAULT_FALLBACK: how many times fallback to normal page
for anonymous mapping.
MCPAGE_ANON_FAULT_CHARGE_FAILED: how many times fallback because of
memcg charge failure.
MCPAGE_ANON_FAULT_PAGE_TABLE_POPULATED: how many times fallback
because page table already populated.
MCPAGE_ANON_FAULT_INSTABLE_ADDRESS_SPACE: how many times fallback
because of unstable address space.
Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
---
include/linux/vm_event_item.h | 10 ++++++++++
mm/mcpage_memory.c | 6 ++++++
mm/memory.c | 1 +
mm/vmstat.c | 7 +++++++
4 files changed, 24 insertions(+)
diff --git a/include/linux/vm_event_item.h b/include/linux/vm_event_item.h
index 7f5d1caf5890..9c36bfc4c904 100644
--- a/include/linux/vm_event_item.h
+++ b/include/linux/vm_event_item.h
@@ -119,6 +119,13 @@ enum vm_event_item { PGPGIN, PGPGOUT, PSWPIN, PSWPOUT,
THP_SWPOUT,
THP_SWPOUT_FALLBACK,
#endif
+#ifdef CONFIG_MCPAGE
+ MCPAGE_ANON_FAULT_ALLOC,
+ MCPAGE_ANON_FAULT_FALLBACK,
+ MCPAGE_ANON_FAULT_CHARGE_FAILED,
+ MCPAGE_ANON_FAULT_PAGE_TABLE_POPULATED,
+ MCPAGE_ANON_FAULT_INSTABLE_ADDRESS_SPACE,
+#endif
#ifdef CONFIG_MEMORY_BALLOON
BALLOON_INFLATE,
BALLOON_DEFLATE,
@@ -159,5 +166,8 @@ enum vm_event_item { PGPGIN, PGPGOUT, PSWPIN, PSWPOUT,
#define THP_FILE_FALLBACK_CHARGE ({ BUILD_BUG(); 0; })
#define THP_FILE_MAPPED ({ BUILD_BUG(); 0; })
#endif
+#ifndef CONFIG_MCPAGE
+#define MCPAGE_ANON_FAULT_FALLBACK ({ BUILD_BUG(); 0; })
+#endif
#endif /* VM_EVENT_ITEM_H_INCLUDED */
diff --git a/mm/mcpage_memory.c b/mm/mcpage_memory.c
index ea4be2e25bce..e208cf818ebf 100644
--- a/mm/mcpage_memory.c
+++ b/mm/mcpage_memory.c
@@ -55,6 +55,7 @@ static vm_fault_t do_anonymous_mcpage(struct vm_fault *vmf,
if (mem_cgroup_charge(page_folio(page), vma->vm_mm, GFP_KERNEL)) {
ret = VM_FAULT_OOM;
+ count_vm_event(MCPAGE_ANON_FAULT_CHARGE_FAILED);
goto oom;
}
@@ -71,12 +72,14 @@ static vm_fault_t do_anonymous_mcpage(struct vm_fault *vmf,
if (!pte_none(*vmf->pte)) {
ret = VM_FAULT_FALLBACK;
update_mmu_cache(vma, addr, vmf->pte);
+ count_vm_event(MCPAGE_ANON_FAULT_PAGE_TABLE_POPULATED);
goto release;
}
ret = check_stable_address_space(vma->vm_mm);
if (ret) {
ret = VM_FAULT_FALLBACK;
+ count_vm_event(MCPAGE_ANON_FAULT_INSTABLE_ADDRESS_SPACE);
goto release;
}
@@ -120,6 +123,9 @@ vm_fault_t do_anonymous_mcpages(struct vm_fault *vmf, unsigned int order)
break;
}
+ if (i == nr)
+ count_vm_event(MCPAGE_ANON_FAULT_ALLOC);
+
while (i < nr)
put_page(&page[i++]);
diff --git a/mm/memory.c b/mm/memory.c
index fb7f370f6c67..b3655be849ae 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -4079,6 +4079,7 @@ static vm_fault_t do_anonymous_page(struct vm_fault *vmf)
if (!(ret & VM_FAULT_FALLBACK))
return ret;
+ count_vm_event(MCPAGE_ANON_FAULT_FALLBACK);
ret = 0;
}
diff --git a/mm/vmstat.c b/mm/vmstat.c
index 1ea6a5ce1c41..c40e33dee1b1 100644
--- a/mm/vmstat.c
+++ b/mm/vmstat.c
@@ -1367,6 +1367,13 @@ const char * const vmstat_text[] = {
"thp_swpout",
"thp_swpout_fallback",
#endif
+#ifdef CONFIG_MCPAGE
+ "mcpage_anon_fault_alloc",
+ "mcpage_anon_fault_fallback",
+ "mcpage_anon_fault_charge_failed",
+ "mcpage_anon_fault_page_table_populated",
+ "mcpage_anon_fault_instable_address_space",
+#endif
#ifdef CONFIG_MEMORY_BALLOON
"balloon_inflate",
"balloon_deflate",
--
2.30.2
next prev parent reply other threads:[~2023-01-09 7:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 7:22 [RFC PATCH 0/4] Multiple consecutive page for anonymous mapping Yin Fengwei
2023-01-09 7:22 ` [RFC PATCH 1/4] mcpage: add size/mask/shift definition for multiple consecutive page Yin Fengwei
2023-01-09 13:24 ` Matthew Wilcox
2023-01-09 16:30 ` Dave Hansen
2023-01-09 17:01 ` Matthew Wilcox
2023-01-10 2:53 ` Yin, Fengwei
2023-01-09 7:22 ` [RFC PATCH 2/4] mcpage: anon page: Use mcpage for anonymous mapping Yin Fengwei
2023-01-09 7:22 ` Yin Fengwei [this message]
2023-01-09 7:22 ` [RFC PATCH 4/4] mcpage: get_unmapped_area return mcpage size aligned addr Yin Fengwei
2023-01-09 8:37 ` [RFC PATCH 0/4] Multiple consecutive page for anonymous mapping Kirill A. Shutemov
2023-01-11 6:13 ` Yin, Fengwei
2023-01-09 17:33 ` David Hildenbrand
2023-01-09 19:11 ` Matthew Wilcox
2023-01-10 14:13 ` David Hildenbrand
2023-01-10 3:57 ` Yin, Fengwei
2023-01-10 14:40 ` David Hildenbrand
2023-01-11 6:12 ` Yin, Fengwei
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=20230109072232.2398464-4-fengwei.yin@intel.com \
--to=fengwei.yin@intel.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=npiggin@gmail.com \
--cc=rppt@kernel.org \
--cc=tim.c.chen@intel.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.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