>Vitor, make sure your processes are never cycled by the scheduler otherwise you'll violate the threading requirements. I'd suggest to just have a single thread for lwip and use a mailbox or similar to trigger certain actions. The OS will take care that you can write into the mailbox from any interrupt/thread/timer.
Hi Jan, I do have a "mailbox", I am using a message-passing OS. All my interrupts just send messages to processes that execute lwIP code, all these processes have the same priority. What do you exactly mean by " never cycle"? The scheduling algo is priority level based, without time-slices. Em sex, 26 de out de 2018 às 15:39, Jan Menzel <men...@peperoni-light.de> escreveu: > > On 26.10.2018 10:27, vr roriz wrote: > >> and only one interrupt runs at a time and isn't interrupted by another > >> interrupt while using > > lwIP - you should be safe. > > > > Simon, could you clarify why nesting interrupts are a problem and > > non-nesting are not? Do you mean that, if an interrupt executes lwIP > > code then it should not be interrupted by another? > > My interrupts never execute lwIP code, they just trigger processes > > that run lwIP, and all of these processes have the same priority. > > Vitor, make sure your processes are never cycled by the scheduler > otherwise you'll violate the threading requirements. I'd suggest to just > have a single thread for lwip and use a mailbox or similar to trigger > certain actions. The OS will take care that you can write into the > mailbox from any interrupt/thread/timer. > > Jan > > _______________________________________________ > 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
