Re: [PATCH v9 08/12] mm/sparsemem: Support sub-section hotplug

2019-06-07 Thread Oscar Salvador
On Fri, 2019-06-07 at 08:38 -0700, Dan Williams wrote: > I don't know, but I can't imagine it would because it's much easier > to > do mem_map relative translations by simple PAGE_OFFSET arithmetic. Yeah, I guess so. > No worries, its a valid question. The bitmap dance is still valid it > will ju

Re: [PATCH v9 08/12] mm/sparsemem: Support sub-section hotplug

2019-06-07 Thread Dan Williams
On Fri, Jun 7, 2019 at 1:34 AM Oscar Salvador wrote: > > On Wed, Jun 05, 2019 at 02:58:42PM -0700, Dan Williams wrote: > > The libnvdimm sub-system has suffered a series of hacks and broken > > workarounds for the memory-hotplug implementation's awkward > > section-aligned (128MB) granularity. For

Re: [PATCH v9 08/12] mm/sparsemem: Support sub-section hotplug

2019-06-07 Thread Oscar Salvador
On Wed, Jun 05, 2019 at 02:58:42PM -0700, Dan Williams wrote: > The libnvdimm sub-system has suffered a series of hacks and broken > workarounds for the memory-hotplug implementation's awkward > section-aligned (128MB) granularity. For example the following backtrace > is emitted when attempting ar

[PATCH v9 08/12] mm/sparsemem: Support sub-section hotplug

2019-06-05 Thread Dan Williams
The libnvdimm sub-system has suffered a series of hacks and broken workarounds for the memory-hotplug implementation's awkward section-aligned (128MB) granularity. For example the following backtrace is emitted when attempting arch_add_memory() with physical address ranges that intersect 'System RA