From: Oscar Salvador <osalvador@techadventures.net>
To: akpm@linux-foundation.org
Cc: mhocko@suse.com, vbabka@suse.cz, pasha.tatashin@oracle.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH 0/4] Small cleanup for memoryhotplug
Date: Mon, 18 Jun 2018 09:13:56 +0200 [thread overview]
Message-ID: <20180618071355.GA18238@techadventures.net> (raw)
In-Reply-To: <20180601125321.30652-1-osalvador@techadventures.net>
On Fri, Jun 01, 2018 at 02:53:17PM +0200, osalvador@techadventures.net wrote:
> From: Oscar Salvador <osalvador@suse.de>
>
>
> Hi,
>
> I wanted to give it a try and do a small cleanup in the memhotplug's code.
> A lot more could be done, but I wanted to start somewhere.
> I tried to unify/remove duplicated code.
>
> The following is what this patchset does:
>
> 1) add_memory_resource() has code to allocate a node in case it was offline.
> Since try_online_node has some code for that as well, I just made add_memory_resource() to
> use that so we can remove duplicated code..
> This is better explained in patch 1/4.
>
> 2) register_mem_sect_under_node() will be called only from link_mem_sections()
>
> 3) Get rid of link_mem_sections() in favour of walk_memory_range() with a callback to
> register_mem_sect_under_node()
>
> 4) Drop unnecessary checks from register_mem_sect_under_node()
>
>
> I have done some tests and I could not see anything broken because of
> this patchset.
>
> Oscar Salvador (4):
> mm/memory_hotplug: Make add_memory_resource use __try_online_node
> mm/memory_hotplug: Call register_mem_sect_under_node
> mm/memory_hotplug: Get rid of link_mem_sections
> mm/memory_hotplug: Drop unnecessary checks from
> register_mem_sect_under_node
>
> drivers/base/memory.c | 2 -
> drivers/base/node.c | 52 +++++---------------------
> include/linux/node.h | 21 +++++------
> mm/memory_hotplug.c | 101 ++++++++++++++++++++++++++------------------------
> 4 files changed, 71 insertions(+), 105 deletions(-)
>
> --
> 2.13.6
>
Hi,
maybe this can get reviewed now that the merge window is closed.
Thanks
Best Regards
Oscar Salvador
next prev parent reply other threads:[~2018-06-18 7:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 12:53 osalvador
2018-06-01 12:53 ` [PATCH 1/4] mm/memory_hotplug: Make add_memory_resource use __try_online_node osalvador
2018-06-07 10:48 ` Jonathan Cameron
2018-06-20 22:18 ` Andrew Morton
2018-06-21 1:41 ` Pavel Tatashin
2018-06-21 7:33 ` Oscar Salvador
2018-06-01 12:53 ` [PATCH 2/4] mm/memory_hotplug: Call register_mem_sect_under_node osalvador
2018-06-21 2:03 ` Pavel Tatashin
2018-06-01 12:53 ` [PATCH 3/4] mm/memory_hotplug: Get rid of link_mem_sections osalvador
2018-06-21 2:35 ` Pavel Tatashin
2018-06-25 17:04 ` Jonathan Cameron
2018-06-25 17:34 ` Oscar Salvador
2018-06-01 12:53 ` [PATCH 4/4] mm/memory_hotplug: Drop unnecessary checks from register_mem_sect_under_node osalvador
2018-06-21 2:38 ` Pavel Tatashin
2018-06-07 10:42 ` [PATCH 0/4] Small cleanup for memoryhotplug Jonathan Cameron
2018-06-07 13:32 ` Oscar Salvador
2018-06-18 7:13 ` Oscar Salvador [this message]
2018-06-21 8:32 ` Michal Hocko
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=20180618071355.GA18238@techadventures.net \
--to=osalvador@techadventures.net \
--cc=akpm@linux-foundation.org \
--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