On Wed, 30 Jan 2013, Tang Chen wrote:
> > Exactly, there is a node 0 but it includes no online memory (and that
> > should be the case as if it was solely hotpluggable memory) at the time of
> > boot. The sysfs interfaces only get added if the memory is onlined later.
>
> OK, you mean you have
It is not node 0, it is whatever node the kernel resides in.
Tang Chen wrote:
>When using movablemem_map=acpi, always set node0 as unhotpluggable,
>otherwise
>if all the memory is hotpluggable, the kernel will fail to boot.
>
>When using movablemem_map=nn[KMG]@ss[KMG], we don't stop users
Hi David,
On 01/30/2013 05:45 PM, David Rientjes wrote:
On Wed, 30 Jan 2013, Tang Chen wrote:
The failure I'm trying to fix is that if all the memory is hotpluggable, and
user
specified movablemem_map, my code will set all the memory as ZONE_MOVABLE, and
kernel
will fail to allocate any
On Wed, 30 Jan 2013, Tang Chen wrote:
> The failure I'm trying to fix is that if all the memory is hotpluggable, and
> user
> specified movablemem_map, my code will set all the memory as ZONE_MOVABLE, and
> kernel
> will fail to allocate any memory, and it will fail to boot.
>
I'm curious, do
On 01/30/2013 04:50 PM, David Rientjes wrote:
On Wed, 30 Jan 2013, Tang Chen wrote:
When using movablemem_map=acpi, always set node0 as unhotpluggable, otherwise
if all the memory is hotpluggable, the kernel will fail to boot.
When using movablemem_map=nn[KMG]@ss[KMG], we don't stop users
On Wed, 30 Jan 2013, Tang Chen wrote:
> When using movablemem_map=acpi, always set node0 as unhotpluggable, otherwise
> if all the memory is hotpluggable, the kernel will fail to boot.
>
> When using movablemem_map=nn[KMG]@ss[KMG], we don't stop users specifying
> node0 as hotpluggable, and
On Wed, 30 Jan 2013, Tang Chen wrote:
When using movablemem_map=acpi, always set node0 as unhotpluggable, otherwise
if all the memory is hotpluggable, the kernel will fail to boot.
When using movablemem_map=nn[KMG]@ss[KMG], we don't stop users specifying
node0 as hotpluggable, and ignore
On 01/30/2013 04:50 PM, David Rientjes wrote:
On Wed, 30 Jan 2013, Tang Chen wrote:
When using movablemem_map=acpi, always set node0 as unhotpluggable, otherwise
if all the memory is hotpluggable, the kernel will fail to boot.
When using movablemem_map=nn[KMG]@ss[KMG], we don't stop users
On Wed, 30 Jan 2013, Tang Chen wrote:
The failure I'm trying to fix is that if all the memory is hotpluggable, and
user
specified movablemem_map, my code will set all the memory as ZONE_MOVABLE, and
kernel
will fail to allocate any memory, and it will fail to boot.
I'm curious, do you
Hi David,
On 01/30/2013 05:45 PM, David Rientjes wrote:
On Wed, 30 Jan 2013, Tang Chen wrote:
The failure I'm trying to fix is that if all the memory is hotpluggable, and
user
specified movablemem_map, my code will set all the memory as ZONE_MOVABLE, and
kernel
will fail to allocate any
It is not node 0, it is whatever node the kernel resides in.
Tang Chen tangc...@cn.fujitsu.com wrote:
When using movablemem_map=acpi, always set node0 as unhotpluggable,
otherwise
if all the memory is hotpluggable, the kernel will fail to boot.
When using movablemem_map=nn[KMG]@ss[KMG], we
On Wed, 30 Jan 2013, Tang Chen wrote:
Exactly, there is a node 0 but it includes no online memory (and that
should be the case as if it was solely hotpluggable memory) at the time of
boot. The sysfs interfaces only get added if the memory is onlined later.
OK, you mean you have only
When using movablemem_map=acpi, always set node0 as unhotpluggable, otherwise
if all the memory is hotpluggable, the kernel will fail to boot.
When using movablemem_map=nn[KMG]@ss[KMG], we don't stop users specifying
node0 as hotpluggable, and ignore all the info in SRAT, so that this option
can
When using movablemem_map=acpi, always set node0 as unhotpluggable, otherwise
if all the memory is hotpluggable, the kernel will fail to boot.
When using movablemem_map=nn[KMG]@ss[KMG], we don't stop users specifying
node0 as hotpluggable, and ignore all the info in SRAT, so that this option
can
14 matches
Mail list logo