linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: 苏辉 <sh_def@163.com>
To: "Mike Rapoport" <rppt@kernel.org>
Cc: "David Rientjes" <rientjes@google.com>,
	akpm@linux-foundation.org,  linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re:Re: [PATCH] mm: remove the redundancy code
Date: Tue, 30 Jun 2020 10:02:24 +0800 (CST)	[thread overview]
Message-ID: <3f4b9136.1440.17302f60674.Coremail.sh_def@163.com> (raw)
In-Reply-To: <20200629202429.GG1492837@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]

I am sorry that i did not consider the memory hotplug case,
and i think we should add a new param to distinguish two different cases.














At 2020-06-30 04:24:29, "Mike Rapoport" <rppt@kernel.org> wrote:
>On Mon, Jun 29, 2020 at 11:50:15AM -0700, David Rientjes wrote:
>> On Tue, 30 Jun 2020, Su Hui wrote:
>> 
>> > remove the redundancy code, the zone_start_pfn
>> > is assigned from zone->zone_start_pfn
>> > Signed-off-by: Su Hui <sh_def@163.com>
>> 
>> I don't think this is redundant, it's used by memory hotplug when onlining 
>> new memory.
>
>Right, it is:
>
>$ git grep -wn init_currently_empty_zone mm/memory_hotplug.c
>mm/memory_hotplug.c:697:            init_currently_empty_zone(zone, start_pfn, nr_pages);
>
>
>> > ---
>> >  mm/page_alloc.c | 2 --
>> >  1 file changed, 2 deletions(-)
>> > 
>> > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
>> > index 3c4eb750a199..3372a8c9fbc4 100644
>> > --- a/mm/page_alloc.c
>> > +++ b/mm/page_alloc.c
>> > @@ -6215,8 +6215,6 @@ void __meminit init_currently_empty_zone(struct zone *zone,
>> >  	if (zone_idx > pgdat->nr_zones)
>> >  		pgdat->nr_zones = zone_idx;
>> >  
>> > -	zone->zone_start_pfn = zone_start_pfn;
>> > -
>> >  	mminit_dprintk(MMINIT_TRACE, "memmap_init",
>> >  			"Initialising map node %d zone %lu pfns %lu -> %lu\n",
>> >  			pgdat->node_id,
>> 
>
>-- 
>Sincerely yours,
>Mike.

[-- Attachment #2: Type: text/html, Size: 2241 bytes --]

  reply	other threads:[~2020-06-30  2:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 17:30 Su Hui
2020-06-29 18:50 ` David Rientjes
2020-06-29 20:24   ` Mike Rapoport
2020-06-30  2:02     ` 苏辉 [this message]
2020-06-30  2:06       ` David Rientjes
2020-06-30 10:28 ` kernel test robot
2020-06-30 11:52 ` kernel test robot
2020-06-30 12:39 ` David Hildenbrand
2020-06-30 13:49   ` 苏辉

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=3f4b9136.1440.17302f60674.Coremail.sh_def@163.com \
    --to=sh_def@163.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --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