From: William Lee Irwin III <wli@holomorphy.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 64GB NUMA-Q after pgcl
Date: Thu, 27 Mar 2003 23:57:30 -0800 [thread overview]
Message-ID: <20030328075730.GP30140@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0303280243080.2884-100000@montezuma.mastecende.com>
On Fri, Mar 28, 2003 at 02:45:30AM -0500, Zwane Mwaikambo wrote:
> before:
> Memory: 65306956k/67100672k available (1724k kernel code, 98252k reserved, 781k data, 284k init, 65134592k highmem)
> after:
> Memory: 65946144k/67100672k available (1956k kernel code, 15936k reserved, 667k data, 300k init, 65198080k highmem)
> Would you mind explaining the details as to what would cause that
> discrepancy in reserved memory size?
Sure. On NUMA-Q mem_map[] is not allocated using bootmem except for
node 0. Various other bootmem allocations are also proportional to
memory as measured in units of PAGE_SIZE, but not all.
So all we're seeing here is node 0's mem_map[] with "miscellaneous"
bootmem allocations thrown in, whether reduced or increased.
This is not very reflective of what's going on as the majority of mem_map[]
is allocated through a custom reservation mechanism as opposed to bootmem.
-- wli
next prev parent reply other threads:[~2003-03-28 7:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 4:00 64GB NUMA-Q after pgcl William Lee Irwin III
2003-03-28 7:45 ` Zwane Mwaikambo
2003-03-28 7:57 ` William Lee Irwin III [this message]
2003-03-28 8:05 ` Zwane Mwaikambo
2003-03-28 10:14 ` William Lee Irwin III
2003-03-28 17:38 ` John Levon
2003-03-30 23:19 ` Andrea Arcangeli
2003-03-31 4:27 ` William Lee Irwin III
2003-03-31 5:22 ` William Lee Irwin III
2003-03-31 21:02 ` Ingo Oeser
2003-03-31 22:27 ` William Lee Irwin III
2003-04-01 1:25 ` Andrea Arcangeli
2003-03-31 18:35 ` Andrea Arcangeli
2003-03-31 18:41 ` Christoph Hellwig
2003-03-31 19:08 ` William Lee Irwin III
2003-04-01 0:47 ` Andrea Arcangeli
2003-04-01 0:44 ` Andrea Arcangeli
2003-03-31 18:55 ` William Lee Irwin III
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=20030328075730.GP30140@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.