Late to the party, but full duplex is first an issue for your hardware and driver. If your hardware is set up to send and receive using DMA, data can be coming in at the same time it is going out. As long as you have enough receive buffers for the largest receive burst, and avoid promiscuous modes...
A single thread processing both directions has a disadvantage only in comparison to a multi-processor system, where you can farm the send and receive to separate cores in true parallel. That's really only needed on extremely high throughput applications, like a switch. On a single core, send and rcv will be ultimately sequential anyway, even if in different threads. HTH! Marty -----Original Message----- From: lwip-users-bounces+martypomeroy=novabio....@nongnu.org [mailto:lwip-users-bounces+martypomeroy=novabio....@nongnu.org] On Behalf Of Shaun Crampton Sent: Tuesday, February 12, 2013 12:03 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] TCP socket thread safety Thanks for the quick response. Duplex communication is pretty important for my application. Is there a way to do it with one of the other APIs (e.g. the raw API)? _______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
