From: Jesper Skov <jskov@redhat.com>
To: "Natarajan, Mekala (CTS)" <NMekala@chn.cognizant.com>
Cc: "'ecos-discuss@sourceware.cygnus.com'"
<ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] memory layout
Date: Tue, 23 Jan 2001 23:46:00 -0000 [thread overview]
Message-ID: <otr91ts89s.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <8F1D166D08ACD41196EE00B0D020944B68B5C2@CTSINENTSXUB>
>>>>> "Natarajan," == Natarajan, Mekala (CTS) <NMekala@chn.cognizant.com> writes:
Natarajan,> is there any option in the kernel configuration so that i
Natarajan,> can reduce the code size.
Yes, many. But if you're looking for this option:
CYGBLD_KERNEL_REDUCE_SIZE_TO_HALF
we took it out a few releases back. We had complaints from MicroSoft
and Wind River about unfair competition. Too bad really.
No, seriously, you need to look at your image (use
'tool-prefix-objdump -D image'). What is taking up the space? If it's
the application, changing the eCos configuration is not going to help.
Of course you can also tweak the kernel, libc, libm, posix, <random
package> options to reduce size. But that require that you read the
option descriptions and decide if it's safe/sensible or not to
disable/enable the option. If you need feature X you can obviously not
disable it to save space.
Jesper
next prev parent reply other threads:[~2001-01-23 23:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 22:51 Natarajan, Mekala (CTS)
2001-01-23 23:46 ` Jesper Skov [this message]
2001-04-18 2:01 [ECOS] Memory Layout james chen
2001-04-18 5:24 ` Gary Thomas
2001-04-18 18:05 ` james chen
2001-04-19 5:12 ` Gary Thomas
2001-04-19 17:37 ` james chen
2001-04-19 17:48 ` Gary Thomas
2002-04-07 16:14 [ECOS] Memory layout Agarwal, Lomesh
2002-04-10 13:51 ` Jonathan Larmour
2002-04-10 14:01 Agarwal, Lomesh
2002-04-10 15:22 ` Jonathan Larmour
2002-04-10 15:31 Agarwal, Lomesh
2002-04-10 17:39 ` Jonathan Larmour
2002-04-10 18:18 Agarwal, Lomesh
2002-04-11 18:03 ` Jonathan Larmour
2002-04-10 18:23 Agarwal, Lomesh
2002-10-30 1:09 [ECOS] memory layout AL Chane
2002-10-30 4:52 ` Chris Garry
2002-10-30 9:55 Schumacher, Gordon
2002-11-04 20:37 ` Jonathan Larmour
2002-11-18 19:44 AL Chane
2003-09-18 7:31 [ECOS] Memory layout Matthieu.GIRARDIN
2003-10-08 14:29 [ECOS] Memory Layout James Yates
2007-10-29 14:13 [ECOS] memory layout Syed Ismail
2007-10-29 14:18 ` Andrew Lunn
2008-04-10 21:35 [ECOS] Memory layout Syed Ismail
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=otr91ts89s.fsf@thinktwice.zoftcorp.dk \
--to=jskov@redhat.com \
--cc=NMekala@chn.cognizant.com \
--cc=ecos-discuss@sourceware.cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).