|Subject:||Re: [lwip-users] ARP message stops TCP?|
|Date:||Thu, 20 Jul 2017 16:28:32 -0500 (CDT)|
After some online digging it looks like I will have problems to work on eventually - for the moment things are working. The call backs are inside the interrupt level, the calls to the library are in the main loop. I don't know what the priority levels are for the interrupts, or if this system allows nesting, so I suspect I'll see weird problems eventually.
Thank you for the warning - when the time comes to rewrite (which always happens!) that will be on top of the list.
On July 20, 2017 at 2:52 PM "address@hidden" <address@hidden> wrote:
Mike Rosing wrote:
I do think the call backs are inside the interrupt
Ehrm, unless everything in lwIP runs on that interrupt level and *not*
in main loop (or a thread), that's OK. If not, sooner or later, you'll
get a problem!
, but the total time is 10's of microseconds and the system response
time is milliseconds, so it should not be an issue.
This doesn't depend on the callback run time vs. system response time.
If it just happens that lwIP is processing timers while your callback
fires, you'll have a problem.
In the end, just don't try to use a library in a way that it wasn't
lwip-users mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|