mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: Mika.Liljeberg@welho.com (Mika Liljeberg)
Cc: ak@muc.de, davem@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: TCP acking too fast
Date: Mon, 15 Oct 2001 22:40:52 +0400 (MSK DST)	[thread overview]
Message-ID: <200110151840.WAA24000@ms2.inr.ac.ru> (raw)
In-Reply-To: <3BC9F029.3897ABE5@welho.com> from "Mika Liljeberg" at Oct 14, 1 11:06:01 pm

Hello!

> Well, I think this "problem" is way overstated.

Understated. :-)

Actually, people who designed all this engine always kept in the mind
only two cases: ftp and telnet. Who did care that some funny
protocols sort of smtp work thousand times slower than they could?
Nobody. Until the time when mail agents started to push really
lots of mails.

> Besides, as I said, you can always disable Nagle

And you will finish with Nagle enabled only on ftp-data. I do not know
another standard protosols which are not broken by delack+nagle. :-)

This is sad but this is already truth: apache, samba etc, even ssh(!),
each of them disable nagle by default, even despite of they are able
to cure this problem with less of damage.

Well, I answered to the question: "tcp is slow!" --- "Guy, you forgot
to enable TCP_NODELAY. TCP is not supposed to work well in your case
without this" so much of times, that started to suspect that nagling
must be disabled by default. It would cause less of troubles. :-)

Alexey

  reply	other threads:[~2001-10-15 18:41 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-14  0:23 Mika Liljeberg
2001-10-14  6:40 ` David S. Miller
2001-10-14  7:05   ` Mika Liljeberg
2001-10-14  7:47   ` David S. Miller
2001-10-14  7:51     ` Mika Liljeberg
2001-10-14  8:12     ` David S. Miller
2001-10-14  8:39       ` Mika Liljeberg
2001-10-14  9:03       ` David S. Miller
2001-10-14  9:15         ` Mika Liljeberg
2001-10-14  9:16         ` David S. Miller
2001-10-14  9:25         ` Andi Kleen
2001-10-14  9:39         ` David S. Miller
2001-10-14 11:30           ` Andi Kleen
2001-10-14 11:49             ` Mika Liljeberg
2001-10-14 14:05               ` Andi Kleen
2001-10-14 14:26                 ` Mika Liljeberg
2001-10-14 16:12                   ` Andi Kleen
2001-10-14 16:55                     ` Mika Liljeberg
2001-10-14 17:07                       ` kuznet
2001-10-14 17:26                         ` Mika Liljeberg
2001-10-14 17:35                           ` kuznet
2001-10-14 17:56                             ` Mika Liljeberg
2001-10-14 18:20                               ` kuznet
2001-10-14 18:48                                 ` Mika Liljeberg
2001-10-14 19:12                                   ` kuznet
2001-10-14 19:32                                     ` Mika Liljeberg
2001-10-14 19:40                                       ` kuznet
2001-10-14 20:06                                         ` Mika Liljeberg
2001-10-15 18:40                                           ` kuznet [this message]
2001-10-15 19:15                                             ` Mika Liljeberg
2001-10-15 19:38                                               ` Mika Liljeberg
2001-10-14 13:14             ` [PATCH] " Mika Liljeberg
2001-10-14 16:36             ` kuznet
2001-10-14  7:50   ` David S. Miller
2001-10-14  7:53     ` Mika Liljeberg
2001-10-15 20:59 ` Bill Davidsen

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=200110151840.WAA24000@ms2.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=Mika.Liljeberg@welho.com \
    --cc=ak@muc.de \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®