* [Linux-ia64] Kernel Resources & Allocation Order
@ 2001-10-18 20:24 Donny Cooper
2001-10-18 22:34 ` KOCHI, Takayoshi
0 siblings, 1 reply; 2+ messages in thread
From: Donny Cooper @ 2001-10-18 20:24 UTC (permalink / raw)
To: linux-ia64
Do kernel-parameters (such as, mem=X and maxcpus=N) have an allocation order according to the physical system layout, or
even follow any order at all?
For example, if I boot with mem\x1024M and maxcpus=2, will resources come from the low number DIMM and CPU slots. Or is
SMP completely random, with no guarantee which resources are allocated. I am aware that you cannot choose which
resources to use, but the documentation I have found on this subject is unclear.
Thanks.
-----------------------------------
Donny Cooper
NEC Systems, Inc.
Advanced Technical Computing Center
dcooper@atcc.necsys.com
www.necservers.com
-----------------------------------
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Linux-ia64] Kernel Resources & Allocation Order
2001-10-18 20:24 [Linux-ia64] Kernel Resources & Allocation Order Donny Cooper
@ 2001-10-18 22:34 ` KOCHI, Takayoshi
0 siblings, 0 replies; 2+ messages in thread
From: KOCHI, Takayoshi @ 2001-10-18 22:34 UTC (permalink / raw)
To: linux-ia64
Hi,
On Thu, 18 Oct 2001 15:24:08 -0500
"Donny Cooper" <dcooper@atcc.necsys.com> wrote:
>
> Do kernel-parameters (such as, mem=X and maxcpus=N) have an allocation order according
> to the physical system layout, or
> even follow any order at all?
Current IA64 Linux implementation uses ACPI MADT order for limiting cpu
number and EFI_MEMMAP order for limiting memory.
The lowest-numberd cpus (except BSP) or the lowest-mapped memory range
is allocated.
> For example, if I boot with mem\x1024M and maxcpus=2, will resources
> come from the low number DIMM and CPU slots. Or is
> SMP completely random, with no guarantee which resources are allocated.
ACPI MADT numbering is dependent on firmware implementation (though
most platform choose the lowest numberd cpu to come first).
Which DIMM is the lowest memory is dependent on hardware
(memory-controller or chipset) and firmware (how to program
memory controller).
> I am aware that you cannot choose which
> resources to use, but the documentation I have found on this subject is unclear.
Rewriting the resource-limiting (maxcpu, maxmem) code, you can control
which part of cpu or memory will be used, but which part of cpu/mem
corresponds to which part of physical cpu/mem is different from
platform to platform.
Regards,
--
KOCHI Takayoshi <t-kouchi@cq.jp.nec.com/t-kouchi@mvf.biglobe.ne.jp>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-10-18 22:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-10-18 20:24 [Linux-ia64] Kernel Resources & Allocation Order Donny Cooper
2001-10-18 22:34 ` KOCHI, Takayoshi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox