From: Wei Yang <richard.weiyang@gmail.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, mhocko@suse.com,
osalvador@suse.de, david@redhat.com
Subject: Re: [PATCH] mm, memory_hotplug: pass next_memory_node to new_page_nodemask()
Date: Thu, 13 Dec 2018 04:03:12 +0000 [thread overview]
Message-ID: <20181213040312.ql6az6spnkpbicjq@master> (raw)
In-Reply-To: <20181213032744.68323-1-richard.weiyang@gmail.com>
On Thu, Dec 13, 2018 at 11:27:44AM +0800, Wei Yang wrote:
>As the document says new_page_nodemask() will try to allocate from a
>different node, but current behavior just do the opposite by passing
>current nid as preferred_nid to new_page_nodemask().
>
Hmm... my understanding is not correct.
Sorry for the broadcasting.
>This patch pass next_memory_node as preferred_nid to new_page_nodemask()
>to fix it.
>
>Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>---
> mm/memory_hotplug.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
>index 6910e0eea074..0c075aac0a81 100644
>--- a/mm/memory_hotplug.c
>+++ b/mm/memory_hotplug.c
>@@ -1335,7 +1335,7 @@ static struct page *new_node_page(struct page *page, unsigned long private)
> if (nodes_empty(nmask))
> node_set(nid, nmask);
>
>- return new_page_nodemask(page, nid, &nmask);
>+ return new_page_nodemask(page, next_memory_node(nid), &nmask);
> }
>
> #define NR_OFFLINE_AT_ONCE_PAGES (256)
>--
>2.15.1
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2018-12-13 4:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 3:27 Wei Yang
2018-12-13 4:03 ` Wei Yang [this message]
2018-12-13 20:10 ` kbuild test robot
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=20181213040312.ql6az6spnkpbicjq@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
/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