Re: [PATCH 03/21] x86, acpi, numa, mem-hotplug: Introduce MEMBLK_HOTPLUGGABLE to reserve hotpluggable memory.

2013-07-23 Thread Tang Chen
On 07/24/2013 03:19 AM, Tejun Heo wrote: On Fri, Jul 19, 2013 at 03:59:16PM +0800, Tang Chen wrote: /* Definition of memblock flags. */ #define MEMBLK_FLAGS_DEFAULT 0x0 /* default flag */ +#define MEMBLK_HOTPLUGGABLE0x1 /* hotpluggable region */ Given that all existing APIs ar

Re: [PATCH 03/21] x86, acpi, numa, mem-hotplug: Introduce MEMBLK_HOTPLUGGABLE to reserve hotpluggable memory.

2013-07-23 Thread Tejun Heo
On Fri, Jul 19, 2013 at 03:59:16PM +0800, Tang Chen wrote: > /* Definition of memblock flags. */ > #define MEMBLK_FLAGS_DEFAULT 0x0 /* default flag */ > +#define MEMBLK_HOTPLUGGABLE 0x1 /* hotpluggable region */ Given that all existing APIs are using "memblock", wouldn't it be better to

[PATCH 03/21] x86, acpi, numa, mem-hotplug: Introduce MEMBLK_HOTPLUGGABLE to reserve hotpluggable memory.

2013-07-19 Thread Tang Chen
Pages used by the kernel cannot be migrated. As a result, hotpluggable memory used by the kernel cannot be hot-removed. So for memory hotplug users, the kernel should not use hotpluggable memory. Since now we have flags in memblock, we introduce a MEMBLK_HOTPLUGGABLE flag to mark hotpluggable memo