From: osalvador@techadventures.net
To: linux-mm@kvack.org
Cc: pasha.tatashin@oracle.com, mhocko@suse.com, vbabka@suse.cz,
akpm@linux-foundation.org, aaron.lu@intel.com,
iamjoonsoo.kim@lge.com, linux-kernel@vger.kernel.org,
Oscar Salvador <osalvador@suse.de>
Subject: [RFC PATCH 0/3] Cleanup for free_area_init_node / free_area_init_core
Date: Tue, 17 Jul 2018 12:56:19 +0200 [thread overview]
Message-ID: <20180717105622.12410-1-osalvador@techadventures.net> (raw)
From: Oscar Salvador <osalvador@suse.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@suse.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
next reply other threads:[~2018-07-17 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 10:56 osalvador [this message]
2018-07-17 10:56 ` [RFC PATCH 1/3] mm: Make free_area_init_core more readable by moving the ifdefs osalvador
2018-07-17 10:56 ` [RFC PATCH 2/3] mm: Refactor free_area_init_core osalvador
2018-07-17 10:56 ` [RFC PATCH 3/3] mm: Make free_area_init_node call certain functions only when booting osalvador
2018-07-18 2:01 ` [RFC PATCH 0/3] Cleanup for free_area_init_node / free_area_init_core Oscar Salvador
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180717105622.12410-1-osalvador@techadventures.net \
--to=osalvador@techadventures.net \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@oracle.com \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox