From: Baruch Even <baruch@ev-en.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@oss.sgi.com, Werner Almesberger <werner@almesberger.net>
Subject: Re: [PATCH] Too aggressive cwnd backoff
Date: Thu, 07 Apr 2005 19:14:45 +0100 [thread overview]
Message-ID: <42557895.8040004@ev-en.org> (raw)
In-Reply-To: <20050407101653.2cc68db1@dxpl.pdx.osdl.net>
Stephen Hemminger wrote:
> On Thu, 7 Apr 2005 19:41:46 +0300
> Baruch Even <baruch@ev-en.org> wrote:
>>The provided patch will set limit to tp->ssthresh. This was the original
>>behaviour in some older version of Linux.
>
> I think this is a real problem, and was observed by Werner with umlsim.
> Don't know when it got introduced because it appears to pre-date the
> '04 work in adding Westwood, BIC, Vegas. Perhaps Alexey can shed some
> light on this.
>
> Going back to the pre-westwood code in BK, the /2 is still there.
This wasn't there in 2.4.23 on which on the original work of H-TCP was
done. I've encountered it in my work on the 2.6.6 version, but didn't
understand all the implications at the time. I've re-encountered it now
that I'm redoing the patches to 2.6.11, and it's as good a time as ever
to resolve it.
The effect is not catastrophic, but it does mean that we leave recovery
into slow-start like ascend of cwnd until we get to ssthresh again. It
does mean that after recovery we inject a lot of packets to the network
at a very fast rate.
Baruch
next prev parent reply other threads:[~2005-04-07 18:14 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 [this message]
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
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=42557895.8040004@ev-en.org \
--to=baruch@ev-en.org \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
--cc=werner@almesberger.net \
/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.