Am 12.01.2019 um 14:20 schrieb Norberto R. de Goes Jr.:
Hi all.
I have used the lwip stack in my project with multithread, no RAM
limitation and running on Linux SO.
Does I need to define LWIP_NETCONN_SEM_PER_THREAD parameter (default =
0) ? Is it recommended or mandatory?
It is recommended because it is faster: without it, socket threads
create a new semaphore for many calls (to synchronize wih tcpip_thread).
By enabling it (and implementing thread-local storage) every thread only
creates one semaphore and reuses it many times.
I question that because I am having crash in
".../lwip/src/api/tcpip.c": LWIP_ASSERT("tcpip_thread: invalid
message", 0);
OBS: msg->type = 2962209658 (invalid)
I don't think this messages is related to LWIP_NETCONN_SEM_PER_THREAD.
How do you come to this conclusion?
Regards,
Simon
Commits in use (SHA-1) :
lwip: c8b65f6c1d2aaa6b3bb1b3d600e54137f294a2d6
lwip-contrib: 4e553f7b3d3af4ac1f3f6c70f38371e4395fdccd
Thanks.
Norberto Goes
--
Norberto R. de Goes Jr.
CPqD - DRC
Tel.: +55 19 3705-4241 / Fax: +55 19 3705-6125
[email protected] <mailto:[email protected]>
www.cpqd.com.br <http://www.cpqd.com.br/>
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
