All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Liljeberg <Mika.Liljeberg@welho.com>
To: kuznet@ms2.inr.ac.ru, ak@muc.de, davem@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: TCP acking too fast
Date: Mon, 15 Oct 2001 22:38:02 +0300	[thread overview]
Message-ID: <3BCB3B1A.B524A605@welho.com> (raw)
In-Reply-To: <200110151840.WAA24000@ms2.inr.ac.ru> <3BCB35CA.4D9D2952@welho.com>

Mika Liljeberg wrote:
> Anyway, it would be interesting to try a (even more) relaxed version of
> Nagle that would allow a maximum of two remnants in flight. This would
> basically cover all TCP request/reply cases (leading AND trailing
> remnant). Coupled with large initial window to get rid of  small-cwnd
> interactions, it might be almost be all right.

Oops, bad idea. You can quench the objections, I already figured out it
won't work. :-(

I guess we're stuck with the current status quo: braindead application
protocols will perform badly no matter what we do. All we can really do
is prevent them harming the network.

Regards,

	MikaL

  reply	other threads:[~2001-10-15 19:38 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-14  0:23 TCP acking too fast 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
2001-10-15 19:15                                                     ` Mika Liljeberg
2001-10-15 19:38                                                       ` Mika Liljeberg [this message]
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=3BCB3B1A.B524A605@welho.com \
    --to=mika.liljeberg@welho.com \
    --cc=ak@muc.de \
    --cc=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.