All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oscar Salvador <osalvador@suse.de>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, david@redhat.com,
	anshuman.khandual@arm.com
Subject: Re: [PATCH v2] mm/sparse: set section nid for hot-add memory
Date: Tue, 18 Jun 2019 09:49:48 +0200	[thread overview]
Message-ID: <20190618074900.GA10030@linux> (raw)
In-Reply-To: <20190618005537.18878-1-richardw.yang@linux.intel.com>

On Tue, Jun 18, 2019 at 08:55:37AM +0800, Wei Yang wrote:
> In case of NODE_NOT_IN_PAGE_FLAGS is set, we store section's node id in
> section_to_node_table[]. While for hot-add memory, this is missed.
> Without this information, page_to_nid() may not give the right node id.
> 
> BTW, current online_pages works because it leverages nid in memory_block.
> But the granularity of node id should be mem_section wide.

I forgot to ask this before, but why do you mention online_pages here?
IMHO, it does not add any value to the changelog, and it does not have much
to do with the matter.

online_pages() works with memblock granularity and not section granularity.
That memblock is just a hot-added range of memory, worth of either 1 section or multiple
sections, depending on the arch or on the size of the current memory.
And we assume that each hot-added memory all belongs to the same node.


> Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
> Reviewed-by: Oscar Salvador <osalvador@suse.de>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
> 
> ---
> v2:
>   * specify the case NODE_NOT_IN_PAGE_FLAGS is effected.
>   * list one of the victim page_to_nid()
> 
> ---
>  mm/sparse.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/mm/sparse.c b/mm/sparse.c
> index 4012d7f50010..48fa16038cf5 100644
> --- a/mm/sparse.c
> +++ b/mm/sparse.c
> @@ -733,6 +733,7 @@ int __meminit sparse_add_one_section(int nid, unsigned long start_pfn,
>  	 */
>  	page_init_poison(memmap, sizeof(struct page) * PAGES_PER_SECTION);
>  
> +	set_section_nid(section_nr, nid);
>  	section_mark_present(ms);
>  	sparse_init_one_section(ms, section_nr, memmap, usemap);
>  
> -- 
> 2.19.1
> 

-- 
Oscar Salvador
SUSE L3


  reply	other threads:[~2019-06-18  7:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  0:55 [PATCH v2] mm/sparse: set section nid for hot-add memory Wei Yang
2019-06-18  7:49 ` Oscar Salvador [this message]
2019-06-18  8:32   ` Wei Yang
2019-06-18  8:40     ` David Hildenbrand
2019-06-19  6:10       ` Michal Hocko
2019-06-19  8:54         ` David Hildenbrand
2019-06-19  9:01           ` Michal Hocko
2019-06-19  9:03             ` David Hildenbrand
2019-06-19  9:08               ` Michal Hocko
2019-06-19  9:11                 ` David Hildenbrand
2019-06-19  6:23 ` Michal Hocko
2019-06-19  7:53   ` Oscar Salvador
2019-06-19  8:51     ` David Hildenbrand
2019-06-19  9:04       ` Michal Hocko
2019-06-19  9:07         ` David Hildenbrand
2019-06-19  9:16           ` Michal Hocko
2019-06-19  9:30             ` David Hildenbrand

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=20190618074900.GA10030@linux \
    --to=osalvador@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=richardw.yang@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.