lwip-users
[Top][All Lists]
Advanced

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

Re: [lwip-users] sys_arch_mbox_fetch() implementation for FreeRTOS


From: massimiliano cialdi
Subject: Re: [lwip-users] sys_arch_mbox_fetch() implementation for FreeRTOS
Date: Wed, 22 Jun 2022 08:49:58 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1

sorry,

my fault


best regards

Max


Massimiliano Cialdi
FIRMWARE ENGINEERING PROFESSIONAL LEADER

Powersoft S.p.A.
Via E. Conti, 5 - Scandicci (Fi) 50018 - Italy
OFFICE:    +39 055 7350230
     



 

On 21/06/22 20:56, goldsimon@gmx.de wrote:
Am 21.06.2022 um 12:37 schrieb massimiliano cialdi via lwip-users:
hello,

the setsockopt(SO_RCVTIMEO) POSIX call contemplates the possibility of
imposing 0 as the 'timeout' parameter, and in that case that socket
becomes non-blocking (See, for example,
https://stackoverflow.com/questions/49706883/disable-socket-timeout-via-setsockopt).


Sorry, but stackoverflow is *not* a good source to cite when talking
about POSIX standard.

Instead, I prefer to search opengroup.com and on the 'setsockopt' page
google gives me
(https://pubs.opengroup.org/onlinepubs/000095399/functions/setsockopt.html),
I find this in the description of SO_RCVTIMEO:

"The default for this option is zero, which indicates that a receive
operation shall not time out."

BTW, even the stackoverflow page you cited says: "If the timeout is set
to zero (the default) then the operation will never timeout".

Regards,
Simon

_______________________________________________
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users

reply via email to

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