[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6552ef9a-ac02-e79f-2eb6-08380ba4b478@linux.ibm.com>
Date: Fri, 11 Sep 2020 18:23:00 +0200
From: Laurent Dufour <ldufour@...ux.ibm.com>
To: David Hildenbrand <david@...hat.com>, akpm@...ux-foundation.org,
Oscar Salvador <osalvador@...e.de>, mhocko@...nel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-mm@...ck.org, "Rafael J . Wysocki" <rafael@...nel.org>,
nathanl@...ux.ibm.com, cheloha@...ux.ibm.com,
Tony Luck <tony.luck@...el.com>,
Fenghua Yu <fenghua.yu@...el.com>, linux-ia64@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] mm: replace memmap_context by memplug_context
Le 11/09/2020 à 16:59, David Hildenbrand a écrit :
>> struct page *start;
>> struct memmap_init_callback_data args;
>> diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h
>> index 375515803cd8..cd2bd21d3a4d 100644
>> --- a/include/linux/memory_hotplug.h
>> +++ b/include/linux/memory_hotplug.h
>> @@ -15,6 +15,15 @@ struct memory_block;
>> struct resource;
>> struct vmem_altmap;
>>
>> +/*
>> + * Memory plugin context, use to differentiate memory added at boot time and
>
> "Memory plugin context" sounds weird.
Any suggestion ?
>> + * hot-plugged memory.
>> + */
>> +enum memplug_context {
>> + MEMPLUG_EARLY,
>> + MEMPLUG_HOTPLUG,
>> +};
>
> Not fully sure this is the right place, though. memory_hotplug.h is
> about MEMPLUG_HOTPLUG only ... I'd leave it at the old spot.
Fair enough.
Powered by blists - more mailing lists