lwip-users
[Top][All Lists]
Advanced

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

[lwip-users] Fw: (no subject)


From: Anirudha Sarangi
Subject: [lwip-users] Fw: (no subject)
Date: Fri, 15 Jul 2011 14:28:24 +0800 (SGT)

Hi Kieren,
I am still struggling with the same issue and my conclusion is it is beyond my capabilities to fix it.
Just to repeat, I am facing an issue with lwip 1.3.0 (and lwip 1.3.2) where my TCP transmission stops after a few hours. My application code is really small to be causing this issue.
Attached is some portion of wireshark capture. I really cant makeout anything from it and it is mainly because I am new to lwip and in general TCP/IP networking. Since I am asked to fix it, I am seeking for help.
 
What my conclusion is, since noone has ever reported such an issue with lwip, it could not be a lwip issue. Since my application does not do great things, it cant be application issue as well. So my suspect is, the way I configure lwip and the way I have ported lwip.
 
Could you take a look at the log and let me know if you could make out anything.
 
regards
Anirudha
 


From: Kieran Mansley <address@hidden>
To: Mailing list for lwIP users <address@hidden>
Sent: Thursday, 7 July 2011 16:27:04
Subject: Re: [lwip-users] (no subject)

On Thu, 2011-07-07 at 18:50 +0800, Anirudha Sarangi wrote:
> Just cross-checked. There is a mistake. With my present timer setup,
> tcp_tmr is
> getting called every 350 msec instead of every 250 msec. Do you think
> it could
> be causing my issue ?

No, the difference between every 350ms and every 250ms would probably be
unnoticable in TCP behaviour (your retransmissions would just start a
few fractions of a second later).

> Then as I understand, once I am in tcp_tmr, I should disable all
> other
> interrupts so that there could be no corruption. Will that be fine?

That's one way.  I prefer to arrange it such that the interrupts do not
call into lwIP, but instead queue work to be processed by the main loop.
You should also worry about application threads calling in, unless you
only call lwIP API functions from the context that is calling tcp_tmr()
in which case they will be naturally excluded.

Kieran


_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users

Attachment: 20110712_2_.pcap
Description: Binary data


reply via email to

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