Hello, but i don´t understand this, your advice, i don't Know about fragmentation, Oscar
On Mon, Oct 5, 2009 at 4:47 PM, Bill Auerbach <[email protected]>wrote: > >As Kieran already said, it is generally a good idea to first get your > >application running with the standard options and once that works begin > >tweaking it to suit your memory/resource needs. MEM_LIBC_MALLOC saves > >you some code-memory if you already use malloc provided by your > >C-library somewhere else (not in lwIP) because you then do not need the > >lwIP heap implementation. On the other hand, memory usage gets a little > >less predictable as you then share the heap with the rest of the code > >running on your target. Thus, this setting largley depends on your > >target. > > I thought I'd ask something that just occurred to me: Can lwIP's > implementation of malloc result in fragmentation of lwIP's heap? > > If it can, than a system requiring 24/7 operation would be better off using > lwIP pools since they cannot fragment. > > Bill > > > > _______________________________________________ > lwip-users mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/lwip-users >
_______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
