Re: [PATCH 2/2] powerpc/nvdimm: Update vmemmap_populated to check sub-section range

2019-09-17 Thread Aneesh Kumar K.V
On 9/16/19 11:16 PM, Dan Williams wrote: On Mon, Sep 9, 2019 at 11:29 PM Aneesh Kumar K.V wrote: With commit: 7cc7867fb061 ("mm/devm_memremap_pages: enable sub-section remap") pmem namespaces are remapped in 2M chunks. On architectures like ppc64 we can map the memmap area using 16MB hugepage

Re: [PATCH 2/2] powerpc/nvdimm: Update vmemmap_populated to check sub-section range

2019-09-16 Thread Oliver O'Halloran
On Tue, Sep 10, 2019 at 4:29 PM Aneesh Kumar K.V wrote: > > With commit: 7cc7867fb061 ("mm/devm_memremap_pages: enable sub-section remap") > pmem namespaces are remapped in 2M chunks. On architectures like ppc64 we > can map the memmap area using 16MB hugepage size and that can cover > a memory

Re: [PATCH 2/2] powerpc/nvdimm: Update vmemmap_populated to check sub-section range

2019-09-16 Thread Dan Williams
On Mon, Sep 9, 2019 at 11:29 PM Aneesh Kumar K.V wrote: > > With commit: 7cc7867fb061 ("mm/devm_memremap_pages: enable sub-section remap") > pmem namespaces are remapped in 2M chunks. On architectures like ppc64 we > can map the memmap area using 16MB hugepage size and that can cover > a memory

[PATCH 2/2] powerpc/nvdimm: Update vmemmap_populated to check sub-section range

2019-09-10 Thread Aneesh Kumar K.V
With commit: 7cc7867fb061 ("mm/devm_memremap_pages: enable sub-section remap") pmem namespaces are remapped in 2M chunks. On architectures like ppc64 we can map the memmap area using 16MB hugepage size and that can cover a memory range of 16G. While enabling new pmem namespaces, since memory is