Re: [lwip-devel] [bug #19345] tcpip_apimsg+api_msg_post problem

[geckook Xu]

If you use the local variable to send tcpip_msg, it would still leave you with
potential problems. because you didn't create an copy for this
variable, the local variable will be unavliable when the program run
to other area.

Do you meet the condition that MEMP_TCP_SEG can not be free in some case.

On 3/21/07, Frédéric Bernon <address@hidden> wrote:
> Follow-up Comment #5, bug #19345 (project lwip):
>
> I join a patch to solve the problem, and to improve reliability (and code is
> more simple).
>
> "api_lib.c, tcpip.c: integrate sys_mbox_fetch(conn->mbox, NULL) calls from
> api_lib.c to tcpip.c's tcpip_apimsg(). Now, use a local variable and not a
> dynamic one from memp to send tcpip_msg to tcpip_thread in a synchrone call.
> Free tcpip_msg from tcpip_apimsg is not done in tcpip_thread. This give a
> faster and more reliable communication between api_lib and tcpip."
>
> Patch file is attached.
>
> If no objection, I will commit it tomorrow...
>
>
> (file #12223)
>    _______________________________________________________
>
> Additional Item Attachment:
>
> File name: tcpip_apimsg.patch             Size:5 KB
>
>
>    _______________________________________________________
>
> Reply to this item at:
>
>  <http://savannah.nongnu.org/bugs/?19345>
>
> _______________________________________________
>  Message posté via/par Savannah
>  http://savannah.nongnu.org/
>
>
>
> _______________________________________________
> lwip-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-devel