From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 48GB NUMA-Q boots, with major IO-APIC hassles
Date: Thu, 27 Mar 2003 21:08:39 -0800 [thread overview]
Message-ID: <20030328050839.GP1350@holomorphy.com> (raw)
In-Reply-To: <20030115105802.GQ940@holomorphy.com>
On Wed, Jan 15, 2003 at 02:58:02AM -0800, William Lee Irwin III wrote:
> Minor extrapolation: aside from potential explosions in very unusual
> corner cases, with these hacks/workarounds 64GB NUMA-Q should boot and
> run (slowly) with an approximate LowTotal of 173296 kB. The main obstacle
> is our setup here would require an additional NR_CPUS > BITS_PER_LONG
> patch, and there isn't much local interest in even seeing whether or how
> poorly it would run without working patches (e.g. hugh's MMUPAGE_SIZE that
> I'm fwd. porting) to do something about runaway mem_map lowmem consumption.
I was only 3MB off wrt. mainline's 64GB LowTotal, not bad at all:
HighTotal: 65134592 kB
HighFree: 65116864 kB
LowTotal: 176076 kB
LowFree: 144180 kB
Turns out NR_CPUS > BITS_PER_LONG was avoided. I'll dig up whatever else
I can here. AIM7 with 10000 tasks and various other things were runnable
on 48GB, but I still need to straighten various fragmentation things out
before benching produces meaningful numbers instead of runs vs. doesn't.
-- wli
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
prev parent reply other threads:[~2003-03-28 5:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 10:58 William Lee Irwin III
2003-01-15 15:24 ` Martin J. Bligh
2003-01-15 15:34 ` William Lee Irwin III
2003-03-28 5:08 ` William Lee Irwin III [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=20030328050839.GP1350@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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