Re: [Patch v2] mm/sparse: only sub-section aligned range would be populated

2020-08-06 Thread Wei Yang
On Thu, Aug 06, 2020 at 09:29:36AM +0200, David Hildenbrand wrote: >On 05.08.20 23:49, Wei Yang wrote: >> On Fri, Jul 03, 2020 at 11:18:28AM +0800, Wei Yang wrote: >>> There are two code path which invoke __populate_section_memmap() >>> >>> * sparse_init_nid() >>> * sparse_add_section() >>> >>> F

Re: [Patch v2] mm/sparse: only sub-section aligned range would be populated

2020-08-06 Thread David Hildenbrand
On 05.08.20 23:49, Wei Yang wrote: > On Fri, Jul 03, 2020 at 11:18:28AM +0800, Wei Yang wrote: >> There are two code path which invoke __populate_section_memmap() >> >> * sparse_init_nid() >> * sparse_add_section() >> >> For both case, we are sure the memory range is sub-section aligned. >> >> *

Re: [Patch v2] mm/sparse: only sub-section aligned range would be populated

2020-08-05 Thread Wei Yang
On Fri, Jul 03, 2020 at 11:18:28AM +0800, Wei Yang wrote: >There are two code path which invoke __populate_section_memmap() > > * sparse_init_nid() > * sparse_add_section() > >For both case, we are sure the memory range is sub-section aligned. > > * we pass PAGES_PER_SECTION to sparse_init_nid()

Re: [Patch v2] mm/sparse: only sub-section aligned range would be populated

2020-07-03 Thread David Hildenbrand
On 03.07.20 05:18, Wei Yang wrote: > There are two code path which invoke __populate_section_memmap() > > * sparse_init_nid() > * sparse_add_section() > > For both case, we are sure the memory range is sub-section aligned. > > * we pass PAGES_PER_SECTION to sparse_init_nid() > * we check

[Patch v2] mm/sparse: only sub-section aligned range would be populated

2020-07-02 Thread Wei Yang
There are two code path which invoke __populate_section_memmap() * sparse_init_nid() * sparse_add_section() For both case, we are sure the memory range is sub-section aligned. * we pass PAGES_PER_SECTION to sparse_init_nid() * we check range by check_pfn_span() before calling sparse_