|Subject:||Re: [lwip-users] Re: lwip-users Digest, Vol 87, Issue 24|
|Date:||Mon, 22 Nov 2010 20:27:01 +0100|
|User-agent:||Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:126.96.36.199) Gecko/20101027 Thunderbird/3.1.6|
lwIP targets embedded systems. The lwIP-internal heap (which can be replaced to use any other heap or the C-library's malloc/free functions) uses MEM_SIZE to define a region of memory that is reserved for the heap when creating the embedded system's memory image. Making this configurable at runtime would mean that all other variables in memory might move. This is not possible, since the linker has to know such sizes in advance.
However, I guess you could reserve the maximum (worst-case) amount for MEM_SIZE and use mem_malloc() to allocate a big memory region from that heap which you can then use for something else if you know that you don't need the full heap for lwIP.
Other than that, as Kieran already said, lwIP provides many other defines to tweak RAM usage, so if you are concerned about memory usage, MEM_SIZE is definitively not the only thing to look at!
I was thinking to change it according to the expected load on my bandwidth
|[Prev in Thread]||Current Thread||[Next in Thread]|