From: Michal Hocko <mhocko@suse.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Haifeng Xu <haifeng.xu@shopee.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/mm_init.c: remove free_area_init_memoryless_node()
Date: Mon, 29 May 2023 13:58:06 +0200 [thread overview]
Message-ID: <ZHSTTu7aNvZeIHIT@dhcp22.suse.cz> (raw)
In-Reply-To: <20230529090446.GK4967@kernel.org>
On Mon 29-05-23 12:04:46, Mike Rapoport wrote:
> (added Michal)
>
> On Sun, May 28, 2023 at 04:57:20AM +0000, Haifeng Xu wrote:
> > free_area_init_memoryless_node() is just a wrapper of
> > free_area_init_node(), remove it to clean up.
> >
> > Signed-off-by: Haifeng Xu <haifeng.xu@shopee.com>
> > ---
> > mm/mm_init.c | 7 +------
> > 1 file changed, 1 insertion(+), 6 deletions(-)
> >
> > diff --git a/mm/mm_init.c b/mm/mm_init.c
> > index 2d91bb52c619..93821824271a 100644
> > --- a/mm/mm_init.c
> > +++ b/mm/mm_init.c
> > @@ -1752,11 +1752,6 @@ void __init setup_nr_node_ids(void)
> > }
> > #endif
> >
> > -static void __init free_area_init_memoryless_node(int nid)
> > -{
> > - free_area_init_node(nid);
> > -}
> > -
> > /*
> > * Some architectures, e.g. ARC may have ZONE_HIGHMEM below ZONE_NORMAL. For
> > * such cases we allow max_zone_pfn sorted in the descending order
> > @@ -1867,7 +1862,7 @@ void __init free_area_init(unsigned long *max_zone_pfn)
> > panic("Cannot allocate %zuB for node %d.\n",
> > sizeof(*pgdat), nid);
> > arch_refresh_nodedata(nid, pgdat);
> > - free_area_init_memoryless_node(nid);
> > + free_area_init_node(nid);
>
> Using a dedicated free_area_init_memoryless_node() wrapper here emphasizes
> that the node has no memory, but I don't have a strong feeling about
> keeping it.
Honestly, I do not think it has any added value anymore. Some time ago
it was a list of special parameters and aliasing that made some sense at
least. Maybe that could be carved into the changelog in some form.
Acked-by: Michal Hocko <mhocko@suse.com>
>
> >
> > /*
> > * We do not want to confuse userspace by sysfs
> > --
> > 2.25.1
> >
>
> --
> Sincerely yours,
> Mike.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2023-05-29 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 4:57 Haifeng Xu
2023-05-29 9:04 ` Mike Rapoport
2023-05-29 11:58 ` Michal Hocko [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=ZHSTTu7aNvZeIHIT@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=haifeng.xu@shopee.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
/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