From: David Miller <davem@davemloft.net>
To: ncardwell@google.com
Cc: netdev@vger.kernel.org, ilpo.jarvinen@helsinki.fi,
nanditad@google.com, ycheng@google.com, hkchu@google.com,
therbert@google.com
Subject: Re: [PATCH 1/2] tcp: fix undo after RTO for BIC
Date: Fri, 20 Jan 2012 14:18:26 -0500 (EST) [thread overview]
Message-ID: <20120120.141826.1023767655731209208.davem@davemloft.net> (raw)
In-Reply-To: <1326944879-22780-1-git-send-email-ncardwell@google.com>
From: Neal Cardwell <ncardwell@google.com>
Date: Wed, 18 Jan 2012 22:47:58 -0500
> This patch fixes BIC so that cwnd reductions made during RTOs can be
> undone (just as they already can be undone when using the default/Reno
> behavior).
>
> When undoing cwnd reductions, BIC-derived congestion control modules
> were restoring the cwnd from last_max_cwnd. There were two problems
> with using last_max_cwnd to restore a cwnd during undo:
>
> (a) last_max_cwnd was set to 0 on state transitions into TCP_CA_Loss
> (by calling the module's reset() functions), so cwnd reductions from
> RTOs could not be undone.
>
> (b) when fast_covergence is enabled (which it is by default)
> last_max_cwnd does not actually hold the value of snd_cwnd before the
> loss; instead, it holds a scaled-down version of snd_cwnd.
>
> This patch makes the following changes:
>
> (1) upon undo, revert snd_cwnd to ca->loss_cwnd, which is already, as
> the existing comment notes, the "congestion window at last loss"
>
> (2) stop forgetting ca->loss_cwnd on TCP_CA_Loss events
>
> (3) use ca->last_max_cwnd to check if we're in slow start
>
> Signed-off-by: Neal Cardwell <ncardwell@google.com>
Applied.
prev parent reply other threads:[~2012-01-20 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 3:47 [PATCH 1/2] tcp: fix undo after RTO for BIC Neal Cardwell
2012-01-19 3:47 ` [PATCH 2/2] tcp: fix undo after RTO for CUBIC Neal Cardwell
2012-01-20 2:49 ` Stephen Hemminger
2012-01-20 19:18 ` David Miller
2012-01-20 19:18 ` David Miller [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=20120120.141826.1023767655731209208.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hkchu@google.com \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=nanditad@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
--cc=ycheng@google.com \
/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).