mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Re: Any good reason why these is so much memory "reserved"?
@ 2000-12-05 10:40 Adam J. Richter
  2000-12-05 12:11 ` Gábor Lénárt
  0 siblings, 1 reply; 4+ messages in thread
From: Adam J. Richter @ 2000-12-05 10:40 UTC (permalink / raw)
  To: lgb; +Cc: linux-kernel

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

Gábor Lénárt writes:
>On Tue, Dec 05, 2000 at 02:18:59AM -0800, Adam J. Richter wrote:
>>       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
>
>I've played with this too. You can't use ramdisk easily on such a system.
[snip]

	We are using such a system and have been for years.
If you'll reread my posting, you will see that it is about relatively
recent changes to the kernel that apparently have broken this.

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/

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Any good reason why these is so much memory "reserved"?
@ 2000-12-05 10:18 Adam J. Richter
  2000-12-05 10:33 ` G?bor L?n?rt
  0 siblings, 1 reply; 4+ messages in thread
From: Adam J. Richter @ 2000-12-05 10:18 UTC (permalink / raw)
  To: linux-kernel

	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/

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2000-12-05 12:42 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-12-05 10:40 Any good reason why these is so much memory "reserved"? Adam J. Richter
2000-12-05 12:11 ` Gábor Lénárt
  -- strict thread matches above, loose matches on Subject: below --
2000-12-05 10:18 Adam J. Richter
2000-12-05 10:33 ` G?bor L?n?rt

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®