[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180717105622.12410-1-osalvador@techadventures.net>
Date: Tue, 17 Jul 2018 12:56:19 +0200
From: osalvador@...hadventures.net
To: linux-mm@...ck.org
Cc: pasha.tatashin@...cle.com, mhocko@...e.com, vbabka@...e.cz,
akpm@...ux-foundation.org, aaron.lu@...el.com,
iamjoonsoo.kim@....com, linux-kernel@...r.kernel.org,
Oscar Salvador <osalvador@...e.de>
Subject: [RFC PATCH 0/3] Cleanup for free_area_init_node / free_area_init_core
From: Oscar Salvador <osalvador@...e.de>
While trying to cleanup the memhotplug code, I found quite difficult to follow
free_area_init_node / free_area_init_core wrt which functions get called
from the memhotplug path.
This is en effort to try to refactor / cleanup those two functions a little bit,
to make them easier to read.
It compiles, but I did not test it.
I would like to get some feedback to see if it is worth or not.
Signed-off-by: Oscar Salvador <osalvador@...e.de>
Oscar Salvador (3):
mm: Make free_area_init_core more readable by moving the ifdefs
mm: Refactor free_area_init_core
mm: Make free_area_init_node call certain functions only when booting
mm/page_alloc.c | 193 ++++++++++++++++++++++++++++++++++----------------------
1 file changed, 116 insertions(+), 77 deletions(-)
--
2.13.6
Powered by blists - more mailing lists