[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #26349] Nagle algorithm doesn't send although segment
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #26349] Nagle algorithm doesn't send although segment is full |
Date: |
Sun, 26 Apr 2009 12:07:00 +0000 |
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; de; rv:1.9.0.9) Gecko/2009040820 Firefox/3.0.9 |
URL:
<http://savannah.nongnu.org/bugs/?26349>
Summary: Nagle algorithm doesn't send although segment is
full
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: goldsimon
Submitted on: So 26 Apr 2009 12:06:59 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: CVS Head
_______________________________________________________
Details:
While debugging the fix for bug #24212 (Deadlocked tcp_retransmit due to
exceeded pcb->cwnd), I discovered that the nagle algorithm doesn't send data
(because unsent->next is null) although the unsent segment is as big as it can
get (i.e. 1460 bytes).
My question is: is this OK? Transmission speed would be better when sending
that packet right away, e.g. based on "unsent->len == pcb->mss", since there
is nothing to be improved here.
However, I don't know what the standards say to this, thus this bug entry to
discuss it.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?26349>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #26349] Nagle algorithm doesn't send although segment is full,
Simon Goldschmidt <=