linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Owen Green <owenjinggreen@yahoo.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Memory usage
Date: Wed, 29 May 2002 15:23:36 -0700 (PDT)	[thread overview]
Message-ID: <20020529222336.30215.qmail@web20102.mail.yahoo.com> (raw)
In-Reply-To: <20020529135428.B3960@home.com>


Hi all,

I`m currently developing applications for a linuxppc
embedded system (mpc8xx) with linux-2.4.4 from denx
and I realised that even with a tiny application I
spent something like 140k on my RAM area, where at
least 100k of that is for ld-2.2.3.so, I guess.
The question is, am I right? Is there a way to share
the code section of ld-2.2.3.so along applications? Is
there a way to get this memory size down?

Thanks in advance,

Owen.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-05-29 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29 19:30 Unrecognized opcode: `mtdcr' Cameron, Steve
2002-05-29 19:54 ` Tom Rini
2002-05-29 20:43   ` Matt Porter
2002-05-29 20:54     ` Matt Porter
2002-05-29 22:23       ` Owen Green [this message]

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=20020529222336.30215.qmail@web20102.mail.yahoo.com \
    --to=owenjinggreen@yahoo.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).