[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] Writing a proxy server - how "non-reentrant" is lwip ra
Re: [lwip-users] Writing a proxy server - how "non-reentrant" is lwip raw API?
Wed, 15 Jun 2011 16:17:40 +0100
On 15 Jun 2011, at 07:07, Peter Montgomery wrote:
> Can I assume that I can call "tcp_write" from the mainline (not lwIP
> interrupt driven) code without problems? My app receives data TCP data using
> a ring buffer that the interrupt driven lwIP code fill, and which is read by
> mainline code. However, my mainline code does reply by directly calling
> "tcp_write." It all seems to work, but I was hoping for clarification.
I'm not 100% sure what your describing, but it sounds to me like you would then
have the potential for two threads ("interrupts" and "mainline") active in the
stack at the same time, which is unlikely to work reliably.