From: Oscar Salvador <osalvador@techadventures.net>
To: Michal Hocko <mhocko@kernel.org>
Cc: akpm@linux-foundation.org, vbabka@suse.cz,
pasha.tatashin@oracle.com, mgorman@techsingularity.net,
aaron.lu@intel.com, iamjoonsoo.kim@lge.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, dan.j.williams@intel.com,
david@redhat.com, Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH v5 4/4] mm/page_alloc: Introduce free_area_init_core_hotplug
Date: Wed, 1 Aug 2018 13:52:54 +0200 [thread overview]
Message-ID: <20180801115254.GA7145@techadventures.net> (raw)
In-Reply-To: <20180801114726.GL16767@dhcp22.suse.cz>
On Wed, Aug 01, 2018 at 01:47:26PM +0200, Michal Hocko wrote:
>
> The split up makes sense to me. Sections attributes can be handled on
> top. Btw. free_area_init_core_hotplug declaration could have gone into
> include/linux/memory_hotplug.h to save the ifdef
You are right, I will fix this up.
>
> > Signed-off-by: Oscar Salvador <osalvador@suse.de>
> > Reviewed-by: Pavel Tatashin <pasha.tatashin@oracle.com>
>
> Acked-by: Michal Hocko <mhocko@suse.com>
Thanks Michal!
Since Pavel and I agreed on putting a patch of his which removes __paginginit
into this patchset, I will send out a v6 in a few minutes.
--
Oscar Salvador
SUSE L3
prev parent reply other threads:[~2018-08-01 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 10:17 [PATCH v5 0/4] Refactor free_area_init_core and add free_area_init_core_hotplug osalvador
2018-07-30 10:17 ` [PATCH v5 1/4] mm/page_alloc: Move ifdefery out of free_area_init_core osalvador
2018-07-30 10:17 ` [PATCH v5 2/4] mm: access zone->node via zone_to_nid() and zone_set_nid() osalvador
2018-07-30 10:17 ` [PATCH v5 3/4] mm/page_alloc: Inline function to handle CONFIG_DEFERRED_STRUCT_PAGE_INIT osalvador
2018-07-30 10:17 ` [PATCH v5 4/4] mm/page_alloc: Introduce free_area_init_core_hotplug osalvador
2018-07-31 10:17 ` Oscar Salvador
2018-07-31 16:12 ` Pavel Tatashin
2018-08-01 12:29 ` Oscar Salvador
2018-08-01 11:47 ` Michal Hocko
2018-08-01 11:52 ` Oscar Salvador [this message]
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=20180801115254.GA7145@techadventures.net \
--to=osalvador@techadventures.net \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).