[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180726073807.GA22028@techadventures.net>
Date: Thu, 26 Jul 2018 09:38:07 +0200
From: Oscar Salvador <osalvador@...hadventures.net>
To: akpm@...ux-foundation.org
Cc: mhocko@...e.com, vbabka@...e.cz, pasha.tatashin@...cle.com,
mgorman@...hsingularity.net, aaron.lu@...el.com,
iamjoonsoo.kim@....com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, dan.j.williams@...el.com,
Oscar Salvador <osalvador@...e.de>
Subject: Re: [PATCH v3 5/5] mm/page_alloc: Introduce memhotplug version of
free_area_init_core
On Thu, Jul 26, 2018 at 12:01:44AM +0200, osalvador@...hadventures.net wrote:
> extern void free_initmem(void);
> +extern void free_area_init_core_hotplug(int nid);
The declaration should be wrapped with an #ifdef CONFIG_MEMORY_HOTPLUG.
> +void __paginginit free_area_init_core_hotplug(int nid)
> +{
> + enum zone_type j;
> + pg_data_t *pgdat = NODE_DATA(nid);
> +
> + pgdat_init_internals(pgdat);
> + for(j = 0; j < MAX_NR_ZONES; j++) {
> + struct zone *zone = pgdat->node_zones + j;
> + zone_init_internals(zone, j, nid, 0);
> + }
> +}
The same applies here
--
Oscar Salvador
SUSE L3
Powered by blists - more mailing lists