[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] Are recv/send/write reentrant if LWIP_NETCONN_FULLDUPLEX en
From: |
Grant Edwards |
Subject: |
[lwip-users] Are recv/send/write reentrant if LWIP_NETCONN_FULLDUPLEX enabled? |
Date: |
Wed, 17 Nov 2021 17:16:18 -0000 (UTC) |
User-agent: |
slrn/1.0.3 (Linux) |
My (newly generated 2.1.3) documentation says that
LWIP_NETCONN_FULLDUPLEX "allows reading from one thread, writing from
a 2nd thread and closing from a 3rd thread". [And the "really alpha"
statement is indeed gone.]
I assume that does not imply that recv/send/write are renntrant such
that two threads could write to a socket/netconn at the same time? Two
sockets reading at the same time is less common, but would be another
example.
This situation doesn't really make much sense for TCP, but I have seen
applications where it is done for UDP and raw Ethernet.
--
Grant
- [lwip-users] Are recv/send/write reentrant if LWIP_NETCONN_FULLDUPLEX enabled?,
Grant Edwards <=