From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] efika memory issues
Date: Wed, 1 Aug 2007 20:27:16 +0200 [thread overview]
Message-ID: <20070801182716.GA12782@aragorn> (raw)
In-Reply-To: <fb412d760708011034l26550f33t1486179d6644b147@mail.gmail.com>
On Wed, Aug 01, 2007 at 12:34:21PM -0500, Hollis Blanchard wrote:
>
> Yup, it's a pain. Here's one idea: set a "GET_HEAP_FROM_WHEREVER"
> flag, then later do
Why a flag? Don't we want to do this unconditionally? MIN_HEAP_SIZE
already determines wether it's appropiate or not.
> We could try doing that in all situations, except:
> - this method isn't often used, so firmwares can have bugs here
Our code already implements most of this (in grub_available_iterate). Why
not doing it ourselves instead of reliing on potentially-broken firmware?
> - if MIN_HEAP_SIZE were small enough (e.g. 2MB), it would mean we
> probably would still have 4MB+ free. However, that depends on the size
> of the modules. I would hate to document "oh, if you can't load your
> OS, try using fewer GRUB modules." On the other hand, we already have
> this problem to some extent: if our modules are too large, we will
> fail to allocate any heap. So maybe this isn't a practical concern.
Yep, the problem already exists. In the end, it's just a matter of which
MIN_HEAP_SIZE do we pick.
--
Robert Millan
My spam trap is honeypot@aybabtu.com. Note: this address is only intended
for spam harvesters. Writing to it will get you added to my black list.
next prev parent reply other threads:[~2007-08-01 18:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 18:16 another regression on Efika Robert Millan
2007-07-02 21:14 ` Robert Millan
2007-07-04 16:18 ` Hollis Blanchard
2007-07-10 10:04 ` Jordi Mallach
2007-07-10 14:08 ` memory management issue (Re: another regression on Efika) Robert Millan
2007-07-10 20:32 ` Hollis Blanchard
2007-07-13 22:08 ` Robert Millan
2007-07-24 19:59 ` Robert Millan
2007-07-25 17:51 ` Hollis Blanchard
2007-07-25 20:08 ` Robert Millan
2007-07-25 23:25 ` Hollis Blanchard
2007-07-27 8:05 ` Robert Millan
[not found] ` <20070727103310.GA1539@powerlinux.fr>
2007-07-27 19:15 ` Robert Millan
2007-07-29 19:30 ` Robert Millan
2007-07-30 20:11 ` [PATCH] efika memory issues Robert Millan
2007-07-30 22:35 ` Hollis Blanchard
2007-07-31 14:38 ` Robert Millan
2007-07-31 15:55 ` Hollis Blanchard
2007-07-31 19:42 ` Robert Millan
2007-08-01 17:34 ` Hollis Blanchard
2007-08-01 18:27 ` Robert Millan [this message]
2007-09-30 20:10 ` [PATCH] fix memory management on efika/pegasos Robert Millan
2007-10-01 18:18 ` Marcin Kurek
2007-10-01 22:25 ` Marcin Kurek
2007-10-02 19:42 ` Robert Millan
2007-10-03 23:38 ` Marcin Kurek
2007-10-04 20:47 ` Robert Millan
2007-07-10 14:10 ` OF disk naming scheme (Re: another regression on Efika) Robert Millan
2007-07-10 19:26 ` Jordi Mallach
2007-07-13 22:16 ` Robert Millan
2007-07-22 9:33 ` Robert Millan
2007-07-22 14:37 ` Marco Gerards
2007-07-22 20:25 ` Robert Millan
2007-08-12 14:56 ` proposed solution using "ofpathname -a" (Re: OF disk naming scheme) Robert Millan
2007-08-05 10:03 ` updated regression diff (Re: another regression on Efika) Robert Millan
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=20070801182716.GA12782@aragorn \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.