From: "Donny Cooper" <dcooper@atcc.necsys.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Kernel Resources & Allocation Order
Date: Thu, 18 Oct 2001 20:24:08 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805368@msgid-missing> (raw)
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
-----------------------------------
next reply other threads:[~2001-10-18 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 20:24 Donny Cooper [this message]
2001-10-18 22:34 ` [Linux-ia64] Kernel Resources & Allocation Order KOCHI, Takayoshi
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-105590698805368@msgid-missing \
--to=dcooper@atcc.necsys.com \
--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