lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] pcb->next points to one of its ancestors causing an end


From: Kieran Mansley
Subject: Re: [lwip-users] pcb->next points to one of its ancestors causing an endless loop
Date: Thu, 07 Jul 2011 13:41:13 +0100

On Thu, 2011-07-07 at 14:08 +0200, brak brak2 wrote:
> If I surround this functions in main thread by
> 
>         SYS_ARCH_DECL_PROTECT(lev);
>         SYS_ARCH_PROTECT(lev);
> 
>         function
> 
>         SYS_ARCH_UNPROTECT(lev);
> 
> will that be enough?

I'm not sure.  It rather depends on your sys_arch's implementation.  If
they exclude interrupts, then it might be enough.

> I don't know that to do with tcp_recved in UART interrupt, because
> when I put it there the data transfer is faster, just as I want. But
> UART interrupt can occure during lwIP core execution.

So don't do that then.  With your current approach you have a choice
between "fast" or "correct".

Kieran




reply via email to

[Prev in Thread] Current Thread [Next in Thread]