[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180718124722.9872-1-osalvador@techadventures.net>
Date: Wed, 18 Jul 2018 14:47:19 +0200
From: osalvador@...hadventures.net
To: akpm@...ux-foundation.org
Cc: pasha.tatashin@...cle.com, mhocko@...e.com, vbabka@...e.cz,
iamjoonsoo.kim@....com, aaron.lu@...el.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Oscar Salvador <osalvador@...e.de>
Subject: [PATCH 0/3] Re-structure free_area_init_node / free_area_init_core
From: Oscar Salvador <osalvador@...e.de>
When free_area_init_node()->free_area_init_core() get called
from memhotplug path, there are some things that we do need to run.
This patchset __pretends__ to make more clear what things get executed
when those two functions get called depending on the context (non-/memhotplug path).
I tested it on x86_64 / powerpc and I did not see anything wrong there.
But some feedback would be appreciated.
We might come up with the conclusion that we can live with the code as it is now.
Oscar Salvador (3):
mm/page_alloc: Move ifdefery out of free_area_init_core
mm/page_alloc: Refactor free_area_init_core
mm/page_alloc: Split context in free_area_init_node
mm/page_alloc.c | 181 +++++++++++++++++++++++++++++++++++---------------------
1 file changed, 114 insertions(+), 67 deletions(-)
--
2.13.6
Powered by blists - more mailing lists