From: Oscar Salvador <osalvador@techadventures.net>
To: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
kirill.shutemov@linux.intel.com, iamjoonsoo.kim@lge.com,
Mel Gorman <mgorman@suse.de>,
Souptick Joarder <jrdr.linux@gmail.com>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
osalvador@suse.de
Subject: Re: [PATCH] mm: make __paginginit based on CONFIG_MEMORY_HOTPLUG
Date: Tue, 31 Jul 2018 16:51:25 +0200 [thread overview]
Message-ID: <20180731145125.GB1499@techadventures.net> (raw)
In-Reply-To: <20180731144545.fh5syvwcecgvqul6@xakep.localdomain>
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@oracle.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@oracle.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
next prev parent reply other threads:[~2018-07-31 14:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 12:45 [PATCH] mm: make __paginginit based on CONFIG_MEMORY_HOTPLUG osalvador
2018-07-31 12:49 ` Pavel Tatashin
2018-07-31 13:04 ` Michal Hocko
2018-07-31 13:17 ` Oscar Salvador
2018-07-31 14:41 ` Oscar Salvador
2018-07-31 14:43 ` Pavel Tatashin
2018-07-31 14:43 ` Pavel Tatashin
2018-07-31 14:45 ` Pavel Tatashin
2018-07-31 14:51 ` Oscar Salvador [this message]
2018-07-31 14:53 ` Pavel Tatashin
2018-07-31 15:01 ` Oscar Salvador
2018-07-31 15:06 ` Pavel Tatashin
2018-07-31 15:23 ` Pavel Tatashin
2018-07-31 20:50 ` Oscar Salvador
2018-07-31 21:33 ` Pavel Tatashin
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=20180731145125.GB1499@techadventures.net \
--to=osalvador@techadventures.net \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jrdr.linux@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).