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: Tue, 27 Oct 2020 16:44:33 +0100 [thread overview]
Message-ID: <daedbc08-7275-40ad-0d07-007ef89ca25f@redhat.com> (raw)
In-Reply-To: <20201027154031.GA11489@linux>
On 27.10.20 16:40, Oscar Salvador wrote:
> On Thu, Oct 22, 2020 at 03:01:44PM +0200, David Hildenbrand wrote:
>>> 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 :)
>
> Yeah, I guess so, but first I would like to have everything else settled.
> So, gentle ping :-)
>
I'm planning on looking into patch #2/3 later this or next week (this
week is open source summit / KVM Forum).
One thing to look into right now is how to make this fly this with
vmemmap optimizations for hugetlb pages.
https://lkml.kernel.org/r/20201026145114.59424-1-songmuchun@bytedance.com
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-10-27 16:40 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 ` [RFC PATCH 0/3] Allocate memmap from hotadded memory (per device) David Hildenbrand
2020-10-27 15:40 ` Oscar Salvador
2020-10-27 15:44 ` David Hildenbrand [this message]
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=daedbc08-7275-40ad-0d07-007ef89ca25f@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 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.