On 21.05.19 18:11, Oscar Salvador wrote:
> On Tue, May 21, 2019 at 12:41:50PM +0200, David Hildenbrand wrote:
>>> +Future Work
>>> +===
>>> +
>>> + - allowing memory hot-add to ZONE_MOVABLE. maybe we need some switch like
>>> +sysctl or new control file.
>>
>> ... that already works if
On Tue, May 21, 2019 at 12:41:50PM +0200, David Hildenbrand wrote:
> > +Future Work
> > +===
> > +
> > + - allowing memory hot-add to ZONE_MOVABLE. maybe we need some switch like
> > +sysctl or new control file.
>
> ... that already works if I am not completely missing the point here
On Tue, May 21, 2019 at 12:41:50PM +0200, David Hildenbrand wrote:
> On 14.05.19 10:23, Mike Rapoport wrote:
> > The "Locking Internals" section of the memory-hotplug documentation is
> > duplicated in admin-guide and core-api. Drop the admin-guide copy as
> > locking internals does not belong ther
On 14.05.19 10:23, Mike Rapoport wrote:
> The "Locking Internals" section of the memory-hotplug documentation is
> duplicated in admin-guide and core-api. Drop the admin-guide copy as
> locking internals does not belong there.
>
> While on it, move the "Future Work" section to the core-api part.
The "Locking Internals" section of the memory-hotplug documentation is
duplicated in admin-guide and core-api. Drop the admin-guide copy as
locking internals does not belong there.
While on it, move the "Future Work" section to the core-api part.
Signed-off-by: Mike Rapoport
---
Documentation/a
