[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #28098] Nagle can prevent fast retransmit from sending
From: |
Harry Bryson |
Subject: |
[lwip-devel] [bug #28098] Nagle can prevent fast retransmit from sending segment |
Date: |
Thu, 26 Nov 2009 11:37:55 +0000 |
User-agent: |
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; GTB6.3; .NET CLR 1.1.4322; MS-RTC LM 8) |
URL:
<http://savannah.nongnu.org/bugs/?28098>
Summary: Nagle can prevent fast retransmit from sending
segment
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: hbryson
Submitted on: Thu 26 Nov 2009 11:37:54 GMT
Category: TCP
Severity: 3 - Normal
Item Group: Faulty Behaviour
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release:
lwIP version: 1.3.1
_______________________________________________________
Details:
If fast retransmit (tcp_rexmit() from tcp_receive()) attempts to output a
segment, the segment can be blocked by Nagle algorithm (if it matches the
appropriate criteria). It should not be.
If a slow retransmission occurs after the above event(tcp_rexmit_rto()), the
previous "stuck" segment is queued behind all its subsequent segments in the
unsent queue. When the unsent queue is output, the "stuck" segment will again
be prevented by Nagle from getting transmitted.
If no sunsequent data is enqueued to TCP (e.g. TCP PCB is "full"), the above
condition is persistent and the connection will stall and eventually fail.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?28098>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #28098] Nagle can prevent fast retransmit from sending segment,
Harry Bryson <=