From: "KOCHI, Takayoshi" <t-kouchi@mvf.biglobe.ne.jp>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Kernel Resources & Allocation Order
Date: Thu, 18 Oct 2001 22:34:53 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805370@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805368@msgid-missing>
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>
prev parent reply other threads:[~2001-10-18 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 20:24 [Linux-ia64] Kernel Resources & Allocation Order Donny Cooper
2001-10-18 22:34 ` KOCHI, Takayoshi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590698805370@msgid-missing \
--to=t-kouchi@mvf.biglobe.ne.jp \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox