From: David Hildenbrand <david@redhat.com>
To: Oscar Salvador <osalvador@suse.de>
Cc: mhocko@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, vbabka@suse.cz, pasha.tatashin@soleen.com
Subject: Re: [RFC PATCH 0/3] Allocate memmap from hotadded memory (per device)
Date: Thu, 22 Oct 2020 15:01:44 +0200 [thread overview]
Message-ID: <3c18e078-25df-3fd4-9988-1b7677d8e05f@redhat.com> (raw)
In-Reply-To: <20201022125835.26396-1-osalvador@suse.de>
> This does not go without saying that the patchset is not 100% complete.
> It is missing:
>
> - a way to disable memmap_on_memory (either sysfs or boot_time cmd)
> - atm, arch_add_memory for s390 screams if an altmap is passed.
> I am still thinking of a way to nicely drop handle that.
> Maybe a function in s390 that sets memmap_on_memory false and
> stuff that check in support_memmap_on_memory function.
Or simply implement altmap support ... shouldn't be too hard :)
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-10-22 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 12:58 [RFC PATCH 0/3] Allocate memmap from hotadded memory (per device) Oscar Salvador
2020-10-22 12:58 ` [RFC PATCH 1/3] mm,memory_hotplug: Introduce MHP_MEMMAP_ON_MEMORY Oscar Salvador
2020-10-22 13:04 ` David Hildenbrand
2020-10-22 12:58 ` [RFC PATCH 2/3] mm: Introduce a new Vmemmap page-type Oscar Salvador
2020-11-20 11:20 ` David Hildenbrand
2020-10-22 12:58 ` [RFC PATCH 3/3] mm,memory_hotplug: Allocate memmap from the added memory range Oscar Salvador
2020-11-17 15:38 ` David Hildenbrand
2020-11-19 10:48 ` Oscar Salvador
2020-11-20 9:31 ` David Hildenbrand
2020-10-22 13:01 ` David Hildenbrand [this message]
2020-10-27 15:40 ` [RFC PATCH 0/3] Allocate memmap from hotadded memory (per device) Oscar Salvador
2020-10-27 15:44 ` David Hildenbrand
2020-10-27 15:58 ` Oscar Salvador
2020-10-28 18:47 ` Mike Kravetz
2020-10-29 7:49 ` 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=3c18e078-25df-3fd4-9988-1b7677d8e05f@redhat.com \
--to=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=vbabka@suse.cz \
/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).