From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Early memory patch, +accounting
Date: 01 Mar 2004 00:06:58 -0700 [thread overview]
Message-ID: <m11xod9hbh.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <403E34B1.3030608@zytor.com>
"H. Peter Anvin" <hpa@zytor.com> writes:
> Eric W. Biederman wrote:
> > I intend to export _end into setup.S so a bootloader can
> > tell what memory the kernel will attempt to use before looking at
> > the e820 map, the kernel command line, and the initrd location.
> > After that the kernel can properly dynamically allocate things.
> >
>
> You're confusing "may" with "will". This is the fundamental problem with this
> approach.
If the margin of error was significant I would agree. The margin of error
in this case is very small.
> > Exporting _end will allow two things.
> > 1) On systems with a 15M-16M I/O hole the bootloader can check to see
> > if a big kernel will attempt to use memory in that region.
> > 2) On small memory systems it will let the bootloader make a good
> > estimate to see if everything will fit into memory.
>
> No, it won't, because it still has no idea whatsoever how much dynamically
> allocated memory it needs during boot.
It will at least ensure the kernel can run long enough to fail gracefully.
I admit that a panic is not the most graceful failure but it does at least
let you know what went wrong.
Eric
next prev parent reply other threads:[~2004-03-01 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 5:10 Early memory patch, revised H. Peter Anvin
2004-02-25 18:26 ` Eric W. Biederman
2004-02-25 18:38 ` H. Peter Anvin
2004-02-25 18:49 ` H. Peter Anvin
2004-02-26 14:56 ` [PATCH] Early memory patch, +accounting Eric W. Biederman
2004-02-26 18:02 ` H. Peter Anvin
2004-03-01 7:06 ` Eric W. Biederman [this message]
2004-02-26 6:16 ` Early memory patch, revised Eric W. Biederman
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=m11xod9hbh.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=hpa@zytor.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®