Re: [lwip-users] Lwip timer ISR priority

[Andrea Merello]

Thank you for your kind explanation!

Just to make sure I've got it; this means also that user APIs like
udp_sendto must be called with ints disabled (or priority rised) when
used in the "main loop" to avoid races with eth ISR and lwip timer
ISR?

Thanks
Andrea

On Wed, Mar 16, 2011 at 2:40 PM, Simon Goldschmidt <address@hidden> wrote:
>
> Andrea Merello <address@hidden> wrote:
>> What are in general the rules about concurrency in lwip for the Enet
>> ISR, the lwip timers etharp_tmr() and tcp_tmr(), and the user APIs ?
>
> lwIP's concurrency rules are very simple: parallel execution of most parts of 
> the stack is *not* allowed. This includes almost everything except the 
> mem(p)_*(), pbuf_*() and sys_*() functions. The netconn- and socket API 
> functions may also be used from multiple threads, however, these have other 
> limitations in that their objects may not be shared among multiple threads.
>
> Simon
> --
> GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit
> gratis Handy-Flat! http://portal.gmx.net/de/go/dsl
>