From: Simon Kallweit <simon.kallweit@intefo.ch>
To: agfa prayoga s <fillariabrancoftii@yahoo.com>
Cc: Sergei Gavrikov <sergei.gavrikov@gmail.com>,
Mandeep Sandhu <mandeepsandhu.chd@gmail.com>,
ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] ecos + lwip
Date: Thu, 27 Aug 2009 14:11:00 -0000 [thread overview]
Message-ID: <4A969535.3060400@intefo.ch> (raw)
In-Reply-To: <144735.17263.qm@web65404.mail.ac4.yahoo.com>
agfa prayoga s wrote:
> Hi all,,,
>
> did lwIP 1.3.0 port that Simon's patched for eCos 3.0 has improvement in
> memory footprint?
>
> i am trying to run httpd example under lwip package on AT91SAM7X-EK board
> filled with AT91SAM7X256. that microcontroller only have 256KB ROM and
> 64KB RAM.
>
> i have compiled the example successfully only with PBUF value 10, disable DHCP,
> SLIP, PPP, raw socket support, IP forwarding.
>
> using arm-eabi-size, httpd binary has size:
> .text : 82740
> .data: 5428
> .bss: 50792
>
> notice that the sum of .data and .bss is almost 56KB, near 64KB.
>
> if i increase the PBUF value over 10(default value is 60), compilation process will failed with error that
> is no longer room in .bss because the limitation in 64KB.
>
> maybe this is out of topic, but i appreciate your assistance...
Well that's hard to say. You would need to ask that question on the lwip
list. I don't know if there are major differences in memory consumption
between lwip 1.1.0 and 1.3.1. One advantage of my port is that it can be
run in a completely polled mode (I call it simple mode), so you can run
all your network code in a single thread, instead of multiple threads
(at least 3). The old port did not directly offer that option. This can
spare you quite a bit of memory (stacks). Notice that when using the
simple mode, you will have to use the raw APIs (see httpd_simple
example) and cannot use the netconn and socket APIs. In my project, I
use the polled mode for the exact same reason (memory) with good results.
Simon
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next parent reply other threads:[~2009-08-27 14:11 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <144735.17263.qm@web65404.mail.ac4.yahoo.com>
2009-08-27 14:11 ` Simon Kallweit [this message]
2009-08-27 14:20 agfa prayoga s
-- strict thread matches above, loose matches on Subject: below --
2009-08-26 11:01 Mandeep Sandhu
2009-08-26 11:16 ` Simon Kallweit
2009-08-27 10:49 ` Mandeep Sandhu
2009-08-27 11:17 ` Simon Kallweit
2009-08-27 12:42 ` Mandeep Sandhu
2009-08-27 13:20 ` Mandeep Sandhu
2009-08-27 13:42 ` Simon Kallweit
2009-08-27 13:51 ` Mandeep Sandhu
2009-08-27 14:02 ` Mandeep Sandhu
2009-08-27 14:06 ` Simon Kallweit
2009-08-27 14:47 ` Sergei Gavrikov
2009-08-27 15:03 ` Sergei Gavrikov
2009-09-01 12:04 ` Mandeep Sandhu
2009-09-01 12:17 ` Simon Kallweit
2009-09-01 12:32 ` Mandeep Sandhu
2009-09-01 12:38 ` Simon Kallweit
2009-09-01 12:49 ` Mandeep Sandhu
2009-09-01 12:57 ` Simon Kallweit
2009-09-01 13:25 ` Mandeep Sandhu
2009-09-01 13:34 ` Simon Kallweit
2009-09-01 15:20 ` Mandeep Sandhu
2009-09-01 15:32 ` Simon Kallweit
2009-09-01 15:46 ` Mandeep Sandhu
2009-09-01 15:49 ` Simon Kallweit
2009-09-02 6:15 ` Mandeep Sandhu
2009-09-02 13:19 ` Mandeep Sandhu
2009-09-02 15:32 ` Simon Kallweit
2009-09-03 7:45 ` Mandeep Sandhu
2009-09-03 8:36 ` Simon Kallweit
2009-09-03 8:46 ` Mandeep Sandhu
2009-09-03 8:48 ` Simon Kallweit
2009-09-03 8:55 ` Mandeep Sandhu
2009-09-03 9:04 ` Simon Kallweit
2009-09-03 10:23 ` Mandeep Sandhu
2009-09-03 10:46 ` Sergei Gavrikov
2009-08-27 13:52 ` Sergei Gavrikov
2009-08-27 14:05 ` Simon Kallweit
2009-08-27 14:42 ` Bart Veer
2009-08-27 14:54 ` Sergei Gavrikov
2009-08-27 13:45 ` Sergei Gavrikov
2009-08-27 13:49 ` Mandeep Sandhu
2009-08-27 14:04 ` Simon Kallweit
2009-07-30 13:10 Mandeep Sandhu
2009-07-30 13:51 ` Sergei Gavrikov
2009-07-31 5:44 ` Mandeep Sandhu
2009-07-31 18:56 ` Sergei Gavrikov
2009-08-02 17:24 ` Mandeep Sandhu
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=4A969535.3060400@intefo.ch \
--to=simon.kallweit@intefo.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=fillariabrancoftii@yahoo.com \
--cc=mandeepsandhu.chd@gmail.com \
--cc=sergei.gavrikov@gmail.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).