[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] Recv en socket TCP

From: Oscar F
Subject: Re: [lwip-users] Recv en socket TCP
Date: Mon, 5 Oct 2009 16:43:54 +0200

Thanks at the moment doesn´t work, not always accept the eight connection, and I never received the one socket. As soon as possible i´ll test to sendo for the other 5 socket. I hope the memory isn´t the problem. at the moment i said to the customer firasr reduce the buffer commnad, because i can´t declare 11000 bytes.

By the other hand, i would like to known how memory using with lwip, freertos,... One question the heap memory are the variables ldeclared in the task head?,  the variables declared into the function and the parameter are using the stack no?

I think i forgot all thing about the micro, ;-). I wish find the solution to my problem and tired an without ideas.

Thanks again

On Mon, Oct 5, 2009 at 4:35 PM, address@hidden <address@hidden> wrote:
Oscar F wrote:
One thing reading the wiki lwip,  do you recommend me use the model of memory MEM_LIBC_MALLOC and forget MEM_SIZE?

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.


lwip-users mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]