Lwip packet processing is done in single thread and hence it's a sequential operation for either incoming or outgoing packets. It may be true.
Regards, Ajay Bhargav On Tue, Nov 16, 2021, 11:17 PM Grant Edwards <grant.b.edwa...@gmail.com> wrote: > I've been reading up on netconn/sockets and thread-safety. At > https://www.nongnu.org/lwip/2_1_x/group__lwip__opts__netconn.html > it says this about the "fullduplex" option: > > "ATTENTION: This is currently really alpha!" > > Is that accurate? > > That presumably applies to the socket api also? > > One of the main industrial protocol stacks we want to run requires > thread-safe socket operations (read from one thread, write from > another), so lwIP stable may not be usable for that product. [I don't > know if "close from a third" is required or not.] > > -- > Grant > > > > > > > _______________________________________________ > lwip-users mailing list > lwip-users@nongnu.org > https://lists.nongnu.org/mailman/listinfo/lwip-users >
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
