[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4jxdhJ0VSViqKxBzD0-H+3dvrWh3OOmM1diX7i_go_4Mg@mail.gmail.com>
Date: Thu, 10 Aug 2017 08:27:56 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: Linux MM <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mgorman@...e.de>, Vlastimil Babka <vbabka@...e.cz>,
Andrea Arcangeli <aarcange@...hat.com>,
Jerome Glisse <jglisse@...hat.com>,
Reza Arbab <arbab@...ux.vnet.ibm.com>,
Yasuaki Ishimatsu <yasu.isimatu@...il.com>,
qiuxishi@...wei.com, Kani Toshimitsu <toshi.kani@....com>,
slaoub@...il.com, Joonsoo Kim <js1304@...il.com>,
Andi Kleen <ak@...ux.intel.com>,
Daniel Kiper <daniel.kiper@...cle.com>,
Igor Mammedov <imammedo@...hat.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Catalin Marinas <catalin.marinas@....com>,
Fenghua Yu <fenghua.yu@...el.com>,
Gerald Schaefer <gerald.schaefer@...ibm.com>,
Heiko Carstens <heiko.carstens@...ibm.com>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Michael Ellerman <mpe@...erman.id.au>,
Paul Mackerras <paulus@...ba.org>,
Thomas Gleixner <tglx@...utronix.de>,
Tony Luck <tony.luck@...el.com>,
Will Deacon <will.deacon@....com>, X86 ML <x86@...nel.org>
Subject: Re: [RFC PATCH v2 0/6] mm, memory_hotplug: allocate memmap from
hotadded memory
On Thu, Aug 10, 2017 at 4:40 AM, Michal Hocko <mhocko@...nel.org> wrote:
> On Tue 08-08-17 13:01:36, Dan Williams wrote:
>> On Mon, Aug 7, 2017 at 12:00 AM, Michal Hocko <mhocko@...nel.org> wrote:
>> > Any comments? Especially for the arch specific? Has anybody had a chance
>> > to test this? I do not want to rush this but I would be really glag if
>> > we could push this work in 4.14 merge window.
>>
>> Hi Michal,
>>
>> I'm interested in taking a look at this especially if we might be able
>> to get rid of vmem_altmap, but this is currently stuck behind some
>> other work in my queue. I'll try to circle back in the next couple
>> weeks.
>
> Well, vmem_altmap was there and easy to reuse. Replacing with something
> else is certainly possible but I really need something to hook a
> dedicated allocator into vmemmap code.
Oh, you're reusing it, that's great. Then I definitely got the wrong
impression from the first glance at the patch set, I'll dig deeper.
Powered by blists - more mailing lists