From: Oscar Salvador <osalvador@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
Michal Hocko <mhocko@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Oscar Salvador <osalvador@suse.de>
Subject: [PATCH v2 0/2] Minor memoryhotplug refactoring
Date: Tue, 21 Jun 2022 06:17:15 +0200 [thread overview]
Message-ID: <20220621041717.6355-1-osalvador@suse.de> (raw)
Hi,
these are a few cleanups.
The first one is to spare us with some operations when dealing with empty nodes,
and the second one is to refactor memory-hotplug code taking advantatge of the
fact that we initialize all nodes (empty or not) when booting the system.
That gives us the chance to only have to reset some fields when the node
goes offline again.
More information can be found in the respective patches.
v1 -> v2:
- Addressed feedback from David
Oscar Salvador (2):
mm/page_alloc: Do not calculate node's total pages and memmap pages
when empty
mm/memory_hotplug: Reset node's state when empty during offline
include/linux/memory_hotplug.h | 2 +-
mm/memory_hotplug.c | 54 ++++++++++++++++------------
mm/page_alloc.c | 65 +++++++++++-----------------------
3 files changed, 53 insertions(+), 68 deletions(-)
--
2.35.3
next reply other threads:[~2022-06-21 4:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 4:17 Oscar Salvador [this message]
2022-06-21 4:17 ` [PATCH v2 1/2] mm/page_alloc: Do not calculate node's total pages and memmap pages when empty Oscar Salvador
2022-06-21 7:44 ` David Hildenbrand
2022-06-22 3:47 ` Oscar Salvador
2022-06-22 3:56 ` Muchun Song
2022-06-22 8:31 ` David Hildenbrand
2022-06-22 8:54 ` Muchun Song
2022-06-22 10:49 ` David Hildenbrand
2022-06-21 4:17 ` [PATCH v2 2/2] mm/memory_hotplug: Reset node's state when empty during offline Oscar Salvador
2022-06-21 7:59 ` David Hildenbrand
2022-06-22 4:25 ` Oscar Salvador
2022-06-22 8:44 ` 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=20220621041717.6355-1-osalvador@suse.de \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@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