lkml.org 
[lkml]   [2006]   [Dec]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: What happened to CONFIG_TCP_NAGLE_OFF?
Alan wrote:
> No it was general purpose. It fixes some extremely bad behaviour in TCP
> with congestion well beyond the "telnet" behaviour.

Saying it is general purpose demeans it. Nagle was created specifically
to deal with the bad behavior that results from IO patterns like those
created by telnet. Obviously other applications can exhibit those same
patterns. Those that do not, have no need for nagle, so they can
benefit from turning it off.

> UDP is rarely appropriate because it has no congestion control. There are
> more appropriate protocols but they are rarely implemented so TCP
> generally gets used.

UDP is highly appropriate because the congestion controls and other
features of TCP are not required for this type of data, and in fact,
tend to muck things up. That is why the application needs to implement
its own congestion, sequencing, retransmit and connect/disconnect
controls; because the way TCP handles them is not good for this
application.

People often use TCP because it is easier, but not optimal.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-12-01 21:45    [W:0.332 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site