LWIP + RTOS - how to avoid netconn block the thread forever?

c network-programming embedded rtos lwip
eepty picture eepty · Jun 1, 2012 · Viewed 12.1k times · Source

When the LwIP netconn_accept() or netconn_recv() function is called, if we are using a RTOS, it will block the thread and wait for a connection until timeout or forever, depends on the setting of LWIP_SO_RCVTIME0. The timeout duration is equal to the SYS_ARCH_TIMEOUT.

The SYS_ARCH_TIMEOUT is defined as 0xffffffff in the core include part of the LwIP stack, so I think it is not expected to be changed.

Actually, I want it to check if a connection is made, if not then it continue the thread. However, if I call netconn_accept(), it will just block the thread and wait there forever (or a very long time)...I don't want to jsut change the define value of SYS_ARCH_TIMEOUT because I need different timeout in different situation...

What is the good way to do that? Thanks.

Answer

Viktor Latypov picture Viktor Latypov · Jun 1, 2012

Polling for TCP connection (or acceptance) is usually a bad practice. Consider spawning a new thread dedicated exclusively to the blocking netconn_accept() call.

I understand the limitations of using RTOSes, but spawning just one helper thread with minimal stack space shouldn't be a major problem.

I believe that implementing a solution to the classical Producer-Consumer problem is not that hard.

If you're talking about the FreeRTOS, it has all the tools needed - semaphores and threads.

Related questions

C: socket connection timeout

I have a simple program to check if a port is open, but I want to shorten the timeout length on the socket connection because the default is far too long. I'm not sure how to do this though. Here's …

Read More
socket connect() vs bind()

Both connect() and bind() system calls 'associate' the socket file descriptor to an address (typically an ip/port combination). Their prototypes are like:- int connect(int sockfd, const struct sockaddr *addr, socklen_t addrlen); and int bind(int sockfd, …

Read More
UNIX nonblocking I/O: O_NONBLOCK vs. FIONBIO

In every example and discussion I run across in the context of BSD socket programming, it seems that the recommended way to set a file descriptor to nonblocking I/O mode is using the O_NONBLOCK flag to fcntl(), e.…

Read More