From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: linux-mm@kvack.org, akpm@linux-foundation.org,
mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
npiggin@gmail.com, christophe.leroy@csgroup.eu
Cc: Oscar Salvador <osalvador@suse.de>,
David Hildenbrand <david@redhat.com>,
Michal Hocko <mhocko@suse.com>,
Vishal Verma <vishal.l.verma@intel.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Subject: [PATCH v8 0/6] Add support for memmap on memory feature on ppc64
Date: Tue, 8 Aug 2023 14:44:55 +0530 [thread overview]
Message-ID: <20230808091501.287660-1-aneesh.kumar@linux.ibm.com> (raw)
This patch series update memmap on memory feature to fall back to
memmap allocation outside the memory block if the alignment rules are
not met. This makes the feature more useful on architectures like
ppc64 where alignment rules are different with 64K page size.
This patch series is dependent on dax vmemmap optimization series
posted here
https://lore.kernel.org/linux-mm/20230718022934.90447-1-aneesh.kumar@linux.ibm.com/
Changes from v7:
* Drop patch 7 because we are still discussing a runtime update of this
feature is useful.
Changes from v6:
* Update comments in the code
* Update commit message for patch 7
Changes from v5:
* Update commit message
* Move memory alloc/free to the callers in patch 6
* Address review feedback w.r.t patch 4
Changes from v4:
* Use altmap.free instead of altmap.reserve
* Address review feedback
Changes from v3:
* Extend the module parameter memmap_on_memory to force allocation even
though we can waste hotplug memory.
Changes from v2:
* Rebase to latest linus tree
* Redo the series based on review feedback. Multiple changes to the patchset.
Changes from v1:
* update the memblock to store vmemmap_altmap details. This is required
so that when we remove the memory we can find the altmap details which
is needed on some architectures.
* rebase to latest linus tree
Aneesh Kumar K.V (6):
mm/memory_hotplug: Simplify ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE kconfig
mm/memory_hotplug: Allow memmap on memory hotplug request to fallback
mm/memory_hotplug: Allow architecture to override memmap on memory
support check
mm/memory_hotplug: Support memmap_on_memory when memmap is not aligned
to pageblocks
powerpc/book3s64/memhotplug: Enable memmap on memory for radix
mm/memory_hotplug: Embed vmem_altmap details in memory block
.../admin-guide/mm/memory-hotplug.rst | 12 ++
arch/arm64/Kconfig | 4 +-
arch/powerpc/Kconfig | 1 +
arch/powerpc/include/asm/pgtable.h | 21 ++
.../platforms/pseries/hotplug-memory.c | 2 +-
arch/x86/Kconfig | 4 +-
drivers/acpi/acpi_memhotplug.c | 3 +-
drivers/base/memory.c | 27 ++-
include/linux/memory.h | 8 +-
include/linux/memory_hotplug.h | 3 +-
mm/Kconfig | 3 +
mm/memory_hotplug.c | 185 ++++++++++++++----
12 files changed, 209 insertions(+), 64 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-08 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 9:14 Aneesh Kumar K.V [this message]
2023-08-08 9:14 ` [PATCH v8 1/6] mm/memory_hotplug: Simplify ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE kconfig Aneesh Kumar K.V
2023-08-08 9:14 ` [PATCH v8 2/6] mm/memory_hotplug: Allow memmap on memory hotplug request to fallback Aneesh Kumar K.V
2023-08-08 9:14 ` [PATCH v8 3/6] mm/memory_hotplug: Allow architecture to override memmap on memory support check Aneesh Kumar K.V
2023-08-08 9:14 ` [PATCH v8 4/6] mm/memory_hotplug: Support memmap_on_memory when memmap is not aligned to pageblocks Aneesh Kumar K.V
2023-08-08 9:15 ` [PATCH v8 5/6] powerpc/book3s64/memhotplug: Enable memmap on memory for radix Aneesh Kumar K.V
2023-08-08 9:15 ` [PATCH v8 6/6] mm/memory_hotplug: Embed vmem_altmap details in memory block Aneesh Kumar K.V
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=20230808091501.287660-1-aneesh.kumar@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@suse.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=osalvador@suse.de \
--cc=vishal.l.verma@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;
as well as URLs for NNTP newsgroup(s).