From: Aneesh Kumar K V <aneesh.kumar@linux.ibm.com>
To: Michal Hocko <mhocko@suse.com>
Cc: David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org, npiggin@gmail.com,
Vishal Verma <vishal.l.verma@intel.com>,
akpm@linux-foundation.org, linuxppc-dev@lists.ozlabs.org,
Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH v7 7/7] mm/memory_hotplug: Enable runtime update of memmap_on_memory parameter
Date: Tue, 1 Aug 2023 14:58:29 +0530 [thread overview]
Message-ID: <a32fe748-fa18-bd92-3a10-5da8dbad96e6@linux.ibm.com> (raw)
In-Reply-To: <ZMjJPFcXlt+aeCUB@dhcp22.suse.cz>
On 8/1/23 2:28 PM, Michal Hocko wrote:
> On Tue 01-08-23 10:11:16, Aneesh Kumar K.V wrote:
>> Allow updating memmap_on_memory mode after the kernel boot. Memory
>> hotplug done after the mode update will use the new mmemap_on_memory
>> value.
>
> Well, this is a user space kABI extension and as such you should spend
> more words about the usecase. Why we could live with this static and now
> need dynamic?
>
This enables easy testing of memmap_on_memory feature without a kernel reboot.
I also expect people wanting to use that when they find dax kmem memory online
failing because of struct page allocation failures[1]. User could reboot back with
memmap_on_memory=y kernel parameter. But being able to enable it via sysfs makes
the feature much more useful.
-aneesh
next prev parent reply other threads:[~2023-08-01 9:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 4:41 [PATCH v7 0/7] Add support for memmap on memory feature on ppc64 Aneesh Kumar K.V
2023-08-01 4:41 ` [PATCH v7 1/7] mm/memory_hotplug: Simplify ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE kconfig Aneesh Kumar K.V
2023-08-01 4:41 ` [PATCH v7 2/7] mm/memory_hotplug: Allow memmap on memory hotplug request to fallback Aneesh Kumar K.V
2023-08-01 4:41 ` [PATCH v7 3/7] mm/memory_hotplug: Allow architecture to override memmap on memory support check Aneesh Kumar K.V
2023-08-01 4:41 ` [PATCH v7 4/7] mm/memory_hotplug: Support memmap_on_memory when memmap is not aligned to pageblocks Aneesh Kumar K.V
2023-08-01 9:04 ` Michal Hocko
2023-08-01 4:41 ` [PATCH v7 5/7] powerpc/book3s64/memhotplug: Enable memmap on memory for radix Aneesh Kumar K.V
2023-08-01 4:41 ` [PATCH v7 6/7] mm/memory_hotplug: Embed vmem_altmap details in memory block Aneesh Kumar K.V
2023-08-01 23:10 ` Verma, Vishal L
2023-08-02 4:47 ` Aneesh Kumar K V
2023-08-01 4:41 ` [PATCH v7 7/7] mm/memory_hotplug: Enable runtime update of memmap_on_memory parameter Aneesh Kumar K.V
2023-08-01 8:58 ` Michal Hocko
2023-08-01 9:28 ` Aneesh Kumar K V [this message]
2023-08-01 10:50 ` Michal Hocko
2023-08-02 4:45 ` Aneesh Kumar K V
2023-08-02 15:50 ` Michal Hocko
2023-08-02 15:54 ` David Hildenbrand
2023-08-02 15:57 ` Aneesh Kumar K V
2023-08-02 16:02 ` Verma, Vishal L
2023-08-02 16:59 ` Michal Hocko
2023-08-03 8:52 ` Michal Hocko
2023-08-03 9:24 ` David Hildenbrand
2023-08-03 11:30 ` Michal Hocko
2023-08-05 14:24 ` Aneesh Kumar K V
2023-08-07 12:27 ` Michal Hocko
2023-08-07 12:41 ` David Hildenbrand
2023-08-07 18:35 ` David Hildenbrand
2023-08-08 6:09 ` Aneesh Kumar K V
2023-08-08 6:29 ` Aneesh Kumar K V
2023-08-08 7:46 ` David Hildenbrand
2023-08-07 12:54 ` David Hildenbrand
2023-08-01 9:07 ` [PATCH v7 0/7] Add support for memmap on memory feature on ppc64 Michal Hocko
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=a32fe748-fa18-bd92-3a10-5da8dbad96e6@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@suse.com \
--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).