[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+CK2bAfw=pkYF2Ux-PM5r7U46JbDA-fM3NjQ3a5F_Fs0D0GHA@mail.gmail.com>
Date: Thu, 2 May 2019 15:28:21 -0400
From: Pavel Tatashin <pasha.tatashin@...een.com>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Michal Hocko <mhocko@...e.com>,
David Hildenbrand <david@...hat.com>,
Logan Gunthorpe <logang@...tatee.com>,
linux-mm <linux-mm@...ck.org>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 05/12] mm/sparsemem: Convert kmalloc_section_memmap()
to populate_section_memmap()
On Wed, Apr 17, 2019 at 2:53 PM Dan Williams <dan.j.williams@...el.com> wrote:
>
> Allow sub-section sized ranges to be added to the memmap.
> populate_section_memmap() takes an explict pfn range rather than
> assuming a full section, and those parameters are plumbed all the way
> through to vmmemap_populate(). There should be no sub-section usage in
> current deployments. New warnings are added to clarify which memmap
> allocation paths are sub-section capable.
>
> Cc: Michal Hocko <mhocko@...e.com>
> Cc: David Hildenbrand <david@...hat.com>
> Cc: Logan Gunthorpe <logang@...tatee.com>
> Signed-off-by: Dan Williams <dan.j.williams@...el.com>
Reviewed-by: Pavel Tatashin <pasha.tatashin@...een.com>
Powered by blists - more mailing lists