From: Oscar Salvador <osalvador@techadventures.net>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: linux-mm@kvack.org, linuxarm@huawei.com
Subject: Re: [RFC] mm/memory_hotplug: wrong node identified if memory was never on-lined.
Date: Tue, 18 Sep 2018 14:13:42 +0200 [thread overview]
Message-ID: <20180918121342.GA29130@techadventures.net> (raw)
In-Reply-To: <20180912150218.00002cbc@huawei.com>
On Wed, Sep 12, 2018 at 03:02:18PM +0100, Jonathan Cameron wrote:
> Now I'm not sure what the preferred fix for this would be.
> 1) Actually set the nid for each pfn during hot add rather than waiting for
> online.
> 2) Modify the whole call chain to pass the nid through as we know it at the
> remove_memory call for hotplug cases...
Hi Jonathan,
I am back from vacation after four weeks, so I might still be in a bubble.
I was cleaning up unregister_mem_sect_under_nodes in [1], but I failed
to see this.
I think that we can pass the node down the chain.
Looking closer, we might be able to get rid of the nodemask var there,
but I need to take a closer look.
I had a RFCv2 sent a month ago [2] to fix another problem.
That patchset, among other things, replaces the zone paramater with the nid.
I was about to send a new version of that patchset, without RFC this time, so
if you do not mind, I could add this change in there and you can comment it.
What do you think?
[1] https://patchwork.kernel.org/patch/10568547/
[2] https://patchwork.kernel.org/patch/10569085/
Thanks
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2018-09-18 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 14:02 [RFC] mm/memory_hotplug: wrong node identified if memory was never on-lined Jonathan Cameron
2018-09-18 12:13 ` Oscar Salvador [this message]
2018-09-18 12:24 ` Jonathan Cameron
2019-03-24 6:12 ` Anshuman Khandual
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=20180918121342.GA29130@techadventures.net \
--to=osalvador@techadventures.net \
--cc=jonathan.cameron@huawei.com \
--cc=linux-mm@kvack.org \
--cc=linuxarm@huawei.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.