From: William Lee Irwin III <wli@holomorphy.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
rpjday@mindspring.com, linux-kernel@vger.kernel.org
Subject: Re: test suite?
Date: Sat, 25 Jan 2003 15:23:06 -0800 [thread overview]
Message-ID: <20030125232306.GZ780@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301252011420.1784-100000@localhost.localdomain>
On Fri, 24 Jan 2003, Randy.Dunlap wrote:
>> Anyone, where is this kernel size limit coming from?
>> System is 8384 kB
>> System is too big. Try using modules.
On Sat, Jan 25, 2003 at 08:22:10PM +0000, Hugh Dickins wrote:
> See pg0 and pg1 in arch/i386/kernel/head.S. There's no technical
> reason (but well-justified resistance to bloat) why pg2... cannot
> be added, but you might find a few little adjustments needed to
> match elsewhere (if you want your testbuild kernel to boot).
It's actually a relatively annoying limit, as various boxen's MP tables
ACPI tables etc. etc. are well above 8MB. At some point one of us should
quash that issue permanently and dynamically map the things. IIRC Linux
needs NUMA-Q boxen to get lynxers reflashed to move MP tables below 8MB
to boot atm. mbligh can more accurate describe the pain involved there.
As for the bzImage, don't bother supporting excess bloat.
All I can say is, "bring me the head of the first moron who shoves some
table needed at boot-time above 4GB".
-- wli
next prev parent reply other threads:[~2003-01-25 23:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1043426077.1620.10.camel@localhost.localdomain>
2003-01-24 17:18 ` test suite? Randy.Dunlap
2003-01-25 1:53 ` Randy.Dunlap
2003-01-25 20:22 ` Hugh Dickins
2003-01-25 22:24 ` Randy.Dunlap
2003-01-25 23:23 ` William Lee Irwin III [this message]
2003-01-25 23:38 ` Martin J. Bligh
2003-01-22 13:44 Robert P. J. Day
2003-01-22 15:59 ` Sam Ravnborg
2003-01-22 16:20 ` Robert P. J. Day
2003-01-22 16:28 ` Cliff White
2003-01-22 17:34 ` Adrian Bunk
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=20030125232306.GZ780@holomorphy.com \
--to=wli@holomorphy.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rpjday@mindspring.com \
/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