linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <boaz@plexistor.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [RFC 1/1] memremap: devm_memremap_pages has wrong nid
Date: Thu, 12 Nov 2015 00:05:01 +0200	[thread overview]
Message-ID: <5643BB8D.4080202@plexistor.com> (raw)
In-Reply-To: <CAPcyv4jCg58-Je4hW=O4TT9ESeJTV-GFEUidLD9n60-z9w9V2Q@mail.gmail.com>

On 11/11/2015 11:46 PM, Dan Williams wrote:
> On Wed, Nov 11, 2015 at 1:16 PM, Boaz Harrosh <boaz@plexistor.com> wrote:
>>
>> The pmem dev as received in devm_memremap_pages() does not have
>> its dev->numa_node properly initialized yet.
>>
>> What I see is that all pmem devices will call arch_add_memory
>> with nid==0 regardless of the real nid the memory is actually
>> on. Needless to say that after that all the NUMA page and zone
>> members (at page->flags) come out wrong.
>>
>> If I do the below code it will all work properly.
>>
>> RFC because probably we want to fix dev->numa_node before the
>> call to devm_memremap_pages.
> 
> Let's just do that instead.  I.e. in the case of NFIT numa node should
> already be set, and in the case of the memmap=ss!nn or e820-type-12 we
> can set the numa node like this:
> 
> diff --git a/drivers/nvdimm/e820.c b/drivers/nvdimm/e820.c
> index 8282db2ef99e..e40df8fedf73 100644
> --- a/drivers/nvdimm/e820.c
> +++ b/drivers/nvdimm/e820.c
> @@ -48,7 +48,7 @@ static int e820_pmem_probe(struct platform_device *pdev)
>                memset(&ndr_desc, 0, sizeof(ndr_desc));
>                ndr_desc.res = p;
>                ndr_desc.attr_groups = e820_pmem_region_attribute_groups;
> -               ndr_desc.numa_node = NUMA_NO_NODE;
> +               ndr_desc.numa_node = memory_add_physaddr_to_nid(p->start);
>                set_bit(ND_REGION_PAGEMAP, &ndr_desc.flags);
>                if (!nvdimm_pmem_region_create(nvdimm_bus, &ndr_desc))
>                        goto err;
> 
> Thanks for pointing out memory_add_physaddr_to_nid(). I did not know
> that existed.
> 

Thanks.

Its kind of late here now, please let me test this tomorrow and come back
to you, but it sounds good, thanks

Boaz


  reply	other threads:[~2015-11-11 22:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 21:16 [RFC 1/1] memremap: devm_memremap_pages has wrong nid Boaz Harrosh
2015-11-11 21:46 ` Dan Williams
2015-11-11 22:05   ` Boaz Harrosh [this message]
2015-11-12 13:10     ` [PATCH] nvdimm: proper NID in e820_pmem_probe Boaz Harrosh
2015-11-12 13:58       ` Boaz Harrosh
2015-11-12 17:13         ` Dan Williams
2015-11-15 10:08           ` Boaz Harrosh
2015-11-13 16:00   ` [RFC 1/1] memremap: devm_memremap_pages has wrong nid Toshi Kani
2015-11-15  9:17     ` Boaz Harrosh
2015-11-16 17:19       ` Toshi Kani
2015-11-17 13:15         ` Boaz Harrosh

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=5643BB8D.4080202@plexistor.com \
    --to=boaz@plexistor.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.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;
as well as URLs for NNTP newsgroup(s).