From: Vincent Pelletier <subdino2004@yahoo.fr>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Huge changes in mm.c
Date: Tue, 12 Jul 2005 13:14:57 +0200 [thread overview]
Message-ID: <42D3A631.50409@yahoo.fr> (raw)
In-Reply-To: <42D26FA4.3010907@inma.ucl.ac.be>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1396 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Vincent Guffens wrote:
> Vincent Pelletier wrote:
> It must be released by the one who called the malloc.
I don't see any good reason to forget - on kernel side - this chunk, as
we still keep the struct member in memory.
Anyway, I've done some other major changes to this patch, now the chunks
are a simple chained list. That prevents bugs like thinking the first
chunk is right after the last one in memory.
The new code is also much lighter on dprintf. I'll send a patch when
I'll have solved what I think is the last bug which only triggers on
x86: malloc returns sometime out of region pointers...
> grub_size_t n = ((size + GRUB_MM_ALIGN - 1) >> GRUB_MM_ALIGN_LOG2) + 1;
> which adds the extra block for the header.
I prefer relying on sizeof when it comes to allocating space instead of
such formula. If we ever change the struct size, it would break in a
strange way - like all memory allocation problems.
Vincent Pelletier
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC06YxFEQoKRQyjtURArzOAKCfGiIOe2uRirlH5UxRum2YzKwXXQCfdxua
ra/FrNuwvA+rG3GpWt7mtZw=
=UP6z
-----END PGP SIGNATURE-----
___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
next prev parent reply other threads:[~2005-07-12 11:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 12:21 [PATCH] Huge changes in mm.c Vincent Pelletier
2005-07-11 12:56 ` Marco Gerards
2005-07-11 13:20 ` Vincent Pelletier
2005-07-11 13:09 ` Vincent Guffens
2005-07-12 11:14 ` Vincent Pelletier [this message]
2005-07-12 10:58 ` Yoshinori K. Okuji
2005-07-12 12:31 ` Vincent Pelletier
2005-07-12 12:55 ` Marco Gerards
2005-07-12 13:41 ` Vincent Pelletier
2005-07-12 15:12 ` Hollis Blanchard
2005-07-12 15:46 ` Marco Gerards
2005-07-12 18:46 ` sparc64 port : diffs to powerpc branches Vincent Pelletier
2005-07-12 19:40 ` Marco Gerards
2005-07-12 20:49 ` Vincent Pelletier
2005-07-13 15:59 ` Marco Gerards
2005-07-13 20:40 ` Vincent Pelletier
2005-07-13 21:27 ` Marco Gerards
2005-07-12 22:17 ` Hollis Blanchard
2005-07-13 1:01 ` common ieee1275 code Hollis Blanchard
2005-07-13 16:13 ` Marco Gerards
2005-07-14 3:38 ` Hollis Blanchard
2005-07-14 9:55 ` Marco Gerards
2005-07-14 14:23 ` Hollis Blanchard
2005-07-14 22:54 ` Vincent Pelletier
2005-07-16 18:45 ` Marco Gerards
2005-07-16 20:10 ` Hollis Blanchard
2005-07-16 22:07 ` Vincent Pelletier
2005-07-18 17:19 ` Marco Gerards
2005-07-18 18:59 ` Hollis Blanchard
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=42D3A631.50409@yahoo.fr \
--to=subdino2004@yahoo.fr \
--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.