netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baruch Even <baruch@ev-en.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: [PATCH] Too aggressive cwnd backoff
Date: Thu, 07 Apr 2005 20:18:09 +0100	[thread overview]
Message-ID: <42558771.1050605@ev-en.org> (raw)
In-Reply-To: <20050407113351.17f8c094.davem@davemloft.net>

David S. Miller wrote:
> On Thu, 7 Apr 2005 19:41:46 +0300
> Baruch Even <baruch@ev-en.org> wrote:
> 
> 
>>However, in tcp_cwnd_down we will not stop reducing the cwnd until we
>>get to limit which is set to tp->ssthresh/2.
>>
>>The provided patch will set limit to tp->ssthresh. This was the original
>>behaviour in some older version of Linux.
> 
> 
> As stated in another email, it is still unknown where this "changed"
> or if it even "changed" at all in the vanilla sources.
> 
> Could you track this down?  I still strongly believe this is some
> WEB100 change you actually had in your tree, or something like
> that.

This change seems to be specific to us (Hamilton), I didn't find it as 
far back as 2.4.12 [1], it wasn't in any 2.6.x kernel and not even in 
web100 version alpha 2.3.2 which corresponds to kernel 2.4.23.

It does appear in the original patches that Doug Leith sent, so the only 
explanation left is that it's something he did in his tree originally. 
And for some reason I believed it was reverting an old change in the 
Linux kernel.

Baruch

[1] ftp.ie.kernel.org is missing 2.4.11 and ketchup died in my hands.

  reply	other threads:[~2005-04-07 19:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-07 16:41 [PATCH] Too aggressive cwnd backoff Baruch Even
2005-04-07 17:16 ` Stephen Hemminger
2005-04-07 18:14   ` Baruch Even
2005-04-07 18:31     ` David S. Miller
2005-04-07 18:37       ` John Heffner
2005-04-08 21:33         ` Baruch Even
2005-04-07 20:26   ` Werner Almesberger
2005-04-07 18:33 ` David S. Miller
2005-04-07 19:18   ` Baruch Even [this message]
2005-04-07 20:37     ` David S. Miller
2005-04-07 21:42   ` Herbert Xu
2005-04-07 21:45     ` David S. Miller

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=42558771.1050605@ev-en.org \
    --to=baruch@ev-en.org \
    --cc=davem@davemloft.net \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).