matiamic commented on issue #16814: URL: https://github.com/apache/nuttx/issues/16814#issuecomment-3247266302
Hi @ken-hutchinson, this seems like the default behavior to me: https://man7.org/linux/man-pages/man2/recv.2.html > If no messages are available at the socket, the receive calls wait for a message to arrive, unless the socket is nonblocking You should be able to go nonblocking by passing the `MSG_DONTWAIT` flag to the `recv`. I am not sure about the blocking of the rest of the network. The behavior is defined [here](https://github.com/apache/nuttx/blob/5592dc75dc5fe03b82acf3a0349bd733099e5d60/net/pkt/pkt_recvmsg.c#L430-L489) I believe. The `net_lock()` is being called, but the lock should be released by the `net_sem_wait` during waiting. But it seems from your description that the netlock might still be locked or there is some other mechanism blocking your ping... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
