From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-kernel@vger.kernel.org
Subject: Any good reason why these is so much memory "reserved"?
Date: Tue, 5 Dec 2000 02:18:59 -0800 [thread overview]
Message-ID: <200012051018.CAA01847@adam.yggdrasil.com> (raw)
Recently, I have had occasion to build a system on a floppy
for a 4MB machine that we use as a router. In the past, the kernels
that we have listed something like 400kB as the amount of memory "reserved"
when they boot. Now, they claim to reserved 4MB when configured with
CONFIG_HIGHMEM4G and 2MB when configured with CONFIG_NOHIGHMEM. The
initial ramdisk then does not have enough space to decompress and the
system halts (out of memory and no killable process). I am tracking
this down and fix it (because the problem of building a small system
has broader application than just this box). My current suspicion is
that it is some problem with the "bootmem" changes of about six
months ago. However, I thought I should post this message, in case
there is some reason why the kernel really does need have to reserve
all of this memory and that I should not try to change things back.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-05 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-05 10:18 Adam J. Richter [this message]
2000-12-05 10:33 ` G?bor L?n?rt
2000-12-05 10:40 Adam J. Richter
2000-12-05 12:11 ` Gábor Lénárt
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=200012051018.CAA01847@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®