From: Phillip Susi <psusi@cfl.rr.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Matt Garman <matthew.garman@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: What happened to CONFIG_TCP_NAGLE_OFF?
Date: Fri, 01 Dec 2006 15:42:45 -0500 [thread overview]
Message-ID: <457093C5.1040501@cfl.rr.com> (raw)
In-Reply-To: <20061201000030.1d8ba600@localhost.localdomain>
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.
next prev parent reply other threads:[~2006-12-01 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 22:05 What happened to CONFIG_TCP_NAGLE_OFF? Matt Garman
2006-11-29 20:06 ` Phillip Susi
2006-11-30 17:21 ` Matt Garman
2006-11-30 19:12 ` John Stoffel
2006-11-30 19:45 ` Phillip Susi
2006-12-01 0:00 ` Alan
2006-12-01 20:42 ` Phillip Susi [this message]
2006-12-02 3:29 ` Herbert Xu
2006-12-04 15:35 ` Phillip Susi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=457093C5.1040501@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox