From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mike Rapoport <rppt@kernel.org>,
Mike Rapoport <rppt@linux.ibm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH 0/2] mm: remove pfn_valid_within() and CONFIG_HOLES_IN_ZONE
Date: Tue, 13 Jul 2021 11:00:33 +0300 [thread overview]
Message-ID: <20210713080035.7464-1-rppt@kernel.org> (raw)
From: Mike Rapoport <rppt@linux.ibm.com>
Hi,
After recent updates to freeing unused parts of the memory map, no
architecture can have holes in the memory map within a pageblock. This
makes pfn_valid_within() check and CONFIG_HOLES_IN_ZONE configuration
option redundant.
The first patch removes them both in a mechanical way and the second patch
simplifies memory_hotplug::test_pages_in_a_zone() that had
pfn_valid_within() surrounded by more logic than simple if.
Mike Rapoport (2):
mm: remove pfn_valid_within() and CONFIG_HOLES_IN_ZONE
mm: memory_hotplug: cleanup after removal of pfn_valid_within()
drivers/base/node.c | 2 --
include/linux/mmzone.h | 12 ------------
mm/Kconfig | 3 ---
mm/compaction.c | 20 +++++++-------------
mm/memory_hotplug.c | 13 +++----------
mm/page_alloc.c | 24 ++----------------------
mm/page_isolation.c | 7 +------
mm/page_owner.c | 14 +-------------
8 files changed, 14 insertions(+), 81 deletions(-)
base-commit: e73f0f0ee7541171d89f2e2491130c7771ba58d3
--
2.28.0
next reply other threads:[~2021-07-13 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 8:00 Mike Rapoport [this message]
2021-07-13 8:00 ` [PATCH 1/2] mm: remove pfn_valid_within() and CONFIG_HOLES_IN_ZONE Mike Rapoport
2021-07-13 9:51 ` David Hildenbrand
2021-07-13 10:22 ` Mike Rapoport
2021-07-13 10:24 ` David Hildenbrand
2021-07-13 20:02 ` Zi Yan
2021-07-13 8:00 ` [PATCH 2/2] mm: memory_hotplug: cleanup after removal of pfn_valid_within() Mike Rapoport
2021-07-13 9:54 ` David Hildenbrand
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=20210713080035.7464-1-rppt@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rafael@kernel.org \
--cc=rppt@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.