mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@deathstar.prodigy.com>
To: linux-kernel@vger.kernel.org
Subject: Re: TCP acking too fast
Date: Mon, 15 Oct 2001 16:59:09 -0400	[thread overview]
Message-ID: <200110152059.f9FKx9q00507@deathstar.prodigy.com> (raw)
In-Reply-To: <3BC8DAF0.3D16A546@welho.com>

In article <3BC8DAF0.3D16A546@welho.com> Mika.Liljeberg@welho.com wrote:

>I've already disabled quickacks, replaced the receive MSS estimate with
>advertised MSS in the ack sending policy (two places), and removed one
>dubious "immediate ack" condition from send_delay_ack(). The annoying
>thing is that none of this seem to make any real difference. I must be
>missing something huge that's right in front of my nose, but I'm
>starting to run out of steam.
>
>Any thoughts on this?

The discussion has been most complete, I guess at this point is you
can't fix the sender to stop this anti-social behaviour, you might try
using iptables to "mangle" the PSH off from this host or rate limit the
ACKs, or some other hack. None of which is a "solution," just some
interesting things to try.

As noted, the core problem is that TCP doesn't like really asymmetric
bandwidth.

-- 
bill davidsen <davidsen@tmr.com>
 "If I were a diplomat, in the best case I'd go hungry.  In the worst
  case, people would die."
		-- Robert Lipe

      parent reply	other threads:[~2001-10-15 20:59 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
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 [this message]

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=200110152059.f9FKx9q00507@deathstar.prodigy.com \
    --to=davidsen@deathstar.prodigy.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®