linux-kernel - Re: [RFC PATCH 0/3] Allocate memmap from hotadded memory (per device)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <daedbc08-7275-40ad-0d07-007ef89ca25f@redhat.com>
Date:   Tue, 27 Oct 2020 16:44:33 +0100
From:   David Hildenbrand <david@...hat.com>
To:     Oscar Salvador <osalvador@...e.de>
Cc:     mhocko@...nel.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, vbabka@...e.cz, pasha.tatashin@...een.com
Subject: Re: [RFC PATCH 0/3] Allocate memmap from hotadded memory (per device)

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