From: Gavin Shan <gshan@redhat.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, alexander.duyck@gmail.com,
akpm@linux-foundation.org, david@redhat.com,
anshuman.khandual@arm.com, catalin.marinas@arm.com,
will@kernel.org, shan.gavin@gmail.com
Subject: [PATCH 0/3] mm/page_reporting: Make page reporting work on arm64 with 64KB page size
Date: Mon, 21 Jun 2021 13:11:49 +0800 [thread overview]
Message-ID: <20210621051152.305224-1-gshan@redhat.com> (raw)
The page reporting threshold is currently equal to @pageblock_order, which
is 13 and 512MB on arm64 with 64KB base page size selected. The page
reporting won't be triggered if the freeing page can't come up with a free
area like that huge. The condition is hard to be met, especially when the
system memory becomes fragmented.
This series intends to solve the issue by having page reporting threshold
as 5 (2MB) on arm64 with 64KB base page size. The patches are organized as:
PATCH[1/3] introduces variable (@page_reporting_order) to replace original
macro (PAGE_REPORTING_MIN_ORDER). It's also exported so that it
can be adjusted at runtime.
PATCH[2/3] renames PAGE_REPORTING_MIN_ORDER with PAGE_REPORTING_ORDER and
allows architecture to specify its own version.
PATCH[3/3] defines PAGE_REPORTING_ORDER to 5, corresponding to 2MB in size,
on arm64 when 64KB base page size is selected. It's still same
as to @pageblock_order for other architectures and cases.
Gavin Shan (3):
mm/page_reporting: Allow to set reporting order
mm/page_reporting: Allow architecture to select reporting order
arm64: mm: Specify smaller page reporting order
Documentation/admin-guide/kernel-parameters.txt | 6 ++++++
arch/arm64/include/asm/page.h | 13 +++++++++++++
mm/page_reporting.c | 8 ++++++--
mm/page_reporting.h | 10 +++++++---
4 files changed, 32 insertions(+), 5 deletions(-)
--
2.23.0
next reply other threads:[~2021-06-21 3:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 5:11 Gavin Shan [this message]
2021-06-21 5:11 ` [PATCH 1/3] mm/page_reporting: Allow to set reporting order Gavin Shan
2021-06-21 5:11 ` [PATCH 2/3] mm/page_reporting: Allow architecture to select " Gavin Shan
2021-06-21 5:11 ` [PATCH 3/3] arm64: mm: Specify smaller page " Gavin Shan
2021-06-21 14:02 ` [PATCH 0/3] mm/page_reporting: Make page reporting work on arm64 with 64KB page size Alexander Duyck
2021-06-21 16:06 ` Michael Kelley
2021-06-22 2:04 ` ** POTENTIAL FRAUD ALERT - RED HAT ** " Gavin Shan
2021-06-22 2:01 ` Gavin Shan
2021-06-22 23:25 Michael Kelley
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=20210621051152.305224-1-gshan@redhat.com \
--to=gshan@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shan.gavin@gmail.com \
--cc=will@kernel.org \
/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).