[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190417150331.90219ca42a1c0db8632d0fd5@linux-foundation.org>
Date: Wed, 17 Apr 2019 15:03:31 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Dan Williams <dan.j.williams@...el.com>
Cc: David Hildenbrand <david@...hat.com>,
Jérôme Glisse <jglisse@...hat.com>,
Logan Gunthorpe <logang@...tatee.com>,
Toshi Kani <toshi.kani@....com>,
Jeff Moyer <jmoyer@...hat.com>, Michal Hocko <mhocko@...e.com>,
Vlastimil Babka <vbabka@...e.cz>, stable@...r.kernel.org,
linux-mm@...ck.org, linux-nvdimm@...ts.01.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 00/12] mm: Sub-section memory hotplug support
On Wed, 17 Apr 2019 11:38:55 -0700 Dan Williams <dan.j.williams@...el.com> wrote:
> The memory hotplug section is an arbitrary / convenient unit for memory
> hotplug. 'Section-size' units have bled into the user interface
> ('memblock' sysfs) and can not be changed without breaking existing
> userspace. The section-size constraint, while mostly benign for typical
> memory hotplug, has and continues to wreak havoc with 'device-memory'
> use cases, persistent memory (pmem) in particular. Recall that pmem uses
> devm_memremap_pages(), and subsequently arch_add_memory(), to allocate a
> 'struct page' memmap for pmem. However, it does not use the 'bottom
> half' of memory hotplug, i.e. never marks pmem pages online and never
> exposes the userspace memblock interface for pmem. This leaves an
> opening to redress the section-size constraint.
v6 and we're not showing any review activity. Who would be suitable
people to help out here?
Powered by blists - more mailing lists