lwip-devel
[Top][All Lists]
Advanced

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

[lwip-devel] [bug #20506] HTTP server doesn't call tcp_output


From: Simon Goldschmidt
Subject: [lwip-devel] [bug #20506] HTTP server doesn't call tcp_output
Date: Fri, 20 Jul 2007 09:00:08 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.5) Gecko/20070713 Firefox/2.0.0.5

Follow-up Comment #29, bug #20506 (project lwip):

That's a good link, indeed. It describes our problem very accurate:

"1.  When the initial window is one segment, a receiver employing
delayed ACKs [RFC1122] is forced to wait for a timeout before
generating an ACK.  With an initial window of at least two
segments, the receiver will generate an ACK after the second data
segment arrives.  This eliminates the wait on the timeout (often
up to 200 msec, and possibly up to 500 msec [RFC1122])."

So, do we set the initial window to 2 mss instead of 1 mss?

If so, would this be in tcp_in.c line 515 (state SYN_SENT) or line 567 (state
SYN_RCVD)? And how do we make sure to set it to 1 mss if a SYN or SYN ACK is
lost? (RFC 3390 says "If the SYN or SYN/ACK is
lost, the initial window used by a sender after a correctly
transmitted SYN MUST be one segment consisting of MSS bytes.")

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?20506>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/





reply via email to

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