From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFT] Re: Policy-based memory allocations (was Re: RFC: 1.97 roadmap)
Date: Mon, 17 Aug 2009 15:04:59 +0200 [thread overview]
Message-ID: <20090817130459.GB32551@thorin> (raw)
In-Reply-To: <d7ead6de0908161235l4603af13iddffb535df0f5a4c@mail.gmail.com>
On Sun, Aug 16, 2009 at 09:35:37PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> Actually I don't understand why it was proposed to include it in 1.97
> at all - it changes memory management, bugs in it are likely to be
> critical and benefit is only smaller core. If it was up to me I would
> just postpone it. But it's possible to put it in 1.97 if someone tests
> it enough.
Well, I was expecting that this wouldn't have to change anything on how the
"normal" heap works. The heap we have now doesn't add low memory to its
arena, so in theory it's possible for another mechanism which reuses the
same functions to use a separate region that doesn't disrupt normal heap
operation in any way.
This solves the problem with bloat in startup.S, which is the reason I
proposed lowmem heap as a feature for 1.97.
But I agree that approaches that change internal heap structures shouldn't
be pushed to 1.97.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-08-17 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 12:45 Policy-based memory allocations (was Re: RFC: 1.97 roadmap) Vladimir 'phcoder' Serbinenko
2009-08-13 20:48 ` Robert Millan
2009-08-13 21:01 ` Vladimir 'phcoder' Serbinenko
2009-08-16 19:35 ` [RFT] " Vladimir 'phcoder' Serbinenko
2009-08-17 13:04 ` Robert Millan [this message]
2009-12-19 19:41 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20090817130459.GB32551@thorin \
--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.