[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180731145125.GB1499@techadventures.net>
Date: Tue, 31 Jul 2018 16:51:25 +0200
From: Oscar Salvador <osalvador@...hadventures.net>
To: Pavel Tatashin <pasha.tatashin@...cle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Michal Hocko <mhocko@...e.com>,
Vlastimil Babka <vbabka@...e.cz>,
kirill.shutemov@...ux.intel.com, iamjoonsoo.kim@....com,
Mel Gorman <mgorman@...e.de>,
Souptick Joarder <jrdr.linux@...il.com>,
Linux Memory Management List <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>, osalvador@...e.de
Subject: Re: [PATCH] mm: make __paginginit based on CONFIG_MEMORY_HOTPLUG
On Tue, Jul 31, 2018 at 10:45:45AM -0400, Pavel Tatashin wrote:
> Here the patch would look like this:
>
> From e640b32dbd329bba5a785cc60050d5d7e1ca18ce Mon Sep 17 00:00:00 2001
> From: Pavel Tatashin <pasha.tatashin@...cle.com>
> Date: Tue, 31 Jul 2018 10:37:44 -0400
> Subject: [PATCH] mm: remove __paginginit
>
> __paginginit is the same thing as __meminit except for platforms without
> sparsemem, there it is defined as __init.
>
> Remove __paginginit and use __meminit. Use __ref in one single function
> that merges __meminit and __init sections: setup_usemap().
>
> Signed-off-by: Pavel Tatashin <pasha.tatashin@...cle.com>
Uhm, I am probably missing something, but with this change, the functions will not be freed up
while freeing init memory, right?
Thanks
--
Oscar Salvador
SUSE L3
Powered by blists - more mailing lists