[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4063e22f-bc33-076d-5300-7bd6e61e3170@intel.com>
Date: Fri, 16 Nov 2018 13:39:26 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Oscar Salvador <osalvador@...e.com>, linux-mm@...ck.org
Cc: mhocko@...e.com, david@...hat.com, rppt@...ux.vnet.ibm.com,
akpm@...ux-foundation.org, arunks@...eaurora.org, bhe@...hat.com,
dan.j.williams@...el.com, Pavel.Tatashin@...rosoft.com,
Jonathan.Cameron@...wei.com, jglisse@...hat.com,
linux-kernel@...r.kernel.org, Oscar Salvador <osalvador@...e.de>
Subject: Re: [RFC PATCH 2/4] mm, memory_hotplug: provide a more generic
restrictions for memory hotplug
On 11/16/18 2:12 AM, Oscar Salvador wrote:
> +/*
> + * Do we want sysfs memblock files created. This will allow userspace to online
> + * and offline memory explicitly. Lack of this bit means that the caller has to
> + * call move_pfn_range_to_zone to finish the initialization.
> + */
> +
> +#define MHP_MEMBLOCK_API 1<<0
> +
> +/* Restrictions for the memory hotplug */
> +struct mhp_restrictions {
> + unsigned long flags; /* MHP_ flags */
> + struct vmem_altmap *altmap; /* use this alternative allocatro for memmaps */
"allocatro" -> "allocator"
Powered by blists - more mailing lists