buglwIP - A Lightweight TCP/IP stack - Bugs: bug #47305, slow load time, DupACK-Problem in...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #47305: slow load time, DupACK-Problem in TCPIP Thread

Submitted by:  Martin Datzmann <martin5523>
Submitted on:  Mon 29 Feb 2016 02:43:05 PM UTC  
 
Category: TCPSeverity: 3 - Normal
Item Group: NoneStatus: Works For Me
Privacy: PublicAssigned to: Simon Goldschmidt <goldsimon>
Open/Closed: ClosedPlanned Release: None
lwIP version: 1.4.1

Fri 04 Mar 2016 08:38:18 PM UTC, comment #1:

This sounds like a misconfiguration (out of memory?) or a bug in your lwIP-port.

Please send questions on how to use lwIP (if this it what you want?) to the
lwip-users list.

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Mon 29 Feb 2016 02:43:05 PM UTC, original submission:

Dear all,

in my project, I use the lwIP-Stack with FreeRTOS on an ARM-Cortex M4 Mikrocontroller.
There is no problem, to serve a small html-page. (web page load time: 3 ms)
When I try to serve a slightly more complex page (html and two pictures), the following problem can occur resulting

in very slow load time:

In response to a request the webserver sends two data-packets (Con1_data1.1/data1.2) as usual and gets an ACK from

the Browser (Con1_ACK1). If an ACK for another TCP-connection (Con2_ACK1) is received between Con1_data1.1/data1.2

and Con1_ACK1, then Con2_ACK1 is handled correctly.

But now, instead of processing Con1_ACK1 and therefore removing Con1_data1.1/data1.2 from the unacked-list, the

TCP/IP-thread is terminating and still waits for an ACK for Con1_data1.1/data1.2. After timeout (ca. 2 s), the

TCP/IP-thread resends Con1_data1.1, gets an ACK again (Con1_ACK1dup) and removes Con1_data1.1 from the unacked-list

and Con1_data1.2 from the unsent-list and everything seems ok.

After this the next two packets are sent (Con1_data2.1/data2.2) and Con1_ACK2 is received. Now in tcp_receive() the

dupack routine is entered probably because of Con1_ACK1dup ( a) dupacks < 3: do nothing) and the TCP/IP-thread is

terminating without removing Con1_data2.1/data2.2 from the unacked-list. From now on the process is repeating again

with resending Con1_data2.1 after timeout and receiving Con1_ACK2dup as described above.

Once the problem occured, it repeats again and again and one has to do a restart to reset the behaviour.
I used lwip 1.4.1 and also latest source from git.savannah.gnu.org (commit #70f3e5e). In both versions the problem

exists.

Has anybody experienced a similar problem with DupACKs here?
What could be the reason for this behaviour?

Thanks!

Martin Datzmann <martin5523>

 

Attached Files
file #36504:  wireshark.jpg added by martin5523 (486KiB - image/jpeg)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by goldsimon (Posted a comment)
  • -unavailable- added by martin5523 (Submitted the item)
  • -unavailable- added by martin5523
  • -unavailable- added by martin5523
  • -unavailable- added by martin5523
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 7 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Fri 04 Mar 2016 08:38:18 PM UTCgoldsimonStatusNone=>Works For Me
      Assigned toNone=>goldsimon
      Open/ClosedOpen=>Closed
    Mon 29 Feb 2016 02:43:05 PM UTCmartin5523Attached File-=>Added wireshark.jpg, #36504
      Carbon-Copy-=>Added -unavailable-
      Carbon-Copy-=>Added -unavailable-
      Carbon-Copy-=>Added -unavailable-

    Back to the top


    Powered by Savane 3.1-cleanup1