From: T Ziomek <ctz001@email.mot.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][PATCH] Update malloc to dlmalloc version 2.8.4
Date: Tue, 7 Jul 2009 14:16:27 -0500 [thread overview]
Message-ID: <20090707191627.GE3979@email.mot.com> (raw)
In-Reply-To: <200907071434.33729.vapier@gentoo.org>
On Tue, Jul 07, 2009 at 02:34:32PM -0400, Mike Frysinger wrote:
> On Tuesday 07 July 2009 12:30:18 Kumar Gala wrote:
> > Here are some size #'s
> >
> > [galak at blarg u-boot-85xx]$ size u-boot
> > text data bss dec hex filename
> > 392040 50536 41957 484533 764b5 u-boot
> > 397660 49500 42397 489557 77855 u-boot (new dlmalloc)
> >
> > [galak at blarg u-boot-85xx]$ size common/dlmalloc.o
> > text data bss dec hex filename
> > 4768 1056 56 5880 16f8 common/dlmalloc.o
> > 10390 16 492 10898 2a92 common/dlmalloc.o (new
> > dlmalloc)
>
> to say it has increased is an understatement. i cant imagine the upstream
> code increasing that much. perhaps we had trimmed/customized the
> implementation so as to shrink it ?
>
> > old dlmalloc:
> > [galak at blarg u-boot-85xx]$ nm --size-sort common/dlmalloc.o
>
> use the bloatcheck script to do a human readable compare between the two
> objects. you can find it in the linux kernel.
And/or, 'pahole' (Poke-a-hole) or some of the other "7 Dwarves" tools
might help shed light on the differences.
LWN article <http://lwn.net/Articles/335942/> (how I heard about them)
GIT <http://git.kernel.org/?p=linux/kernel/git/acme/pahole.git>
OLS '07 paper <http://oops.ghostprotocols.net:81/acme/7dwarves.pdf> or
<http://ols.fedoraproject.org/OLS/Reprints-2007/melo-Reprint.pdf>
Tom
--
It is of fundamental importance to understand |
that the primary recipient of your source code | Email to 'CTZ001'
is not the compiler but your coworkers. | at 'email.mot.com'
-- KreaTV SW Dev Guidelines |
next prev parent reply other threads:[~2009-07-07 19:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 16:27 [U-Boot] [RFC][PATCH] Update malloc to dlmalloc version 2.8.4 Kumar Gala
2009-07-07 16:30 ` Kumar Gala
2009-07-07 18:34 ` Mike Frysinger
2009-07-07 19:16 ` T Ziomek [this message]
2009-07-07 19:50 ` Kumar Gala
2009-07-07 20:02 ` Scott Wood
2009-07-07 20:22 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-07 20:25 ` Scott Wood
2009-07-07 22:24 ` Kumar Gala
2009-07-08 5:58 ` Mike Frysinger
2009-07-08 6:22 ` Robin Getz
2009-07-08 6:58 ` Peter Tyser
2009-07-08 18:57 ` Mike Frysinger
2009-07-07 20:39 ` T Ziomek
2009-07-07 20:47 ` Kim Phillips
2009-07-07 19:49 ` Kumar Gala
2009-07-08 4:37 ` Robin Getz
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=20090707191627.GE3979@email.mot.com \
--to=ctz001@email.mot.com \
--cc=u-boot@lists.denx.de \
/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