From: "Zimmermann, Alexander" <Alexander.Zimmermann@netapp.com>
To: "raffaello@erg.abdn.ac.uk" <raffaello@erg.abdn.ac.uk>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"ziaul.hossain@abdn.ac.uk" <ziaul.hossain@abdn.ac.uk>,
Fairhurst Gorry <gorry@erg.abdn.ac.uk>
Subject: Re: [PATCH 1/1] TCP NewCWV for Linux
Date: Fri, 21 Feb 2014 08:16:36 +0000 [thread overview]
Message-ID: <4C5CF805-D1A6-4DC1-B48F-F3D145C54C58@netapp.com> (raw)
In-Reply-To: <bbf79368e5d6514fbe6704a77b473407.squirrel@blake.erg.abdn.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
Hi,
Am 20.02.2014 um 20:28 schrieb Raffaello@erg.abdn.ac.uk:
> Hi,
>
> This is a patch for newcwv a TCP sender-side modification,
> currently a work item at TCPM (TCP Maintenance and Minor extensions)
> at the IETF:
>
> http://tools.ietf.org/search/draft-ietf-tcpm-newcwv-05
>
> newcwv aims to supersede CWV (RFC2861) to provide better
> congestion control for rate-limited applications that use TCP.
>
> We implemented it as a module that uses tcp_congestion_ops.
This implies that we cannot use NewCWV w/ any other CC algo than
NewReno. Please correct me if I’m wrong, but this is not what we
(finally) would like to have. The NewCWV implementation should be
CC independent.
Alex
> The main changes are in "cong_avoid" before Reno cwnd control
> and at the start and end of Fast Retransmit:
>
> 1) Before Reno algorithm we estimate at each ACK our pipeACK
> (update_pipeack) and decide to increase or not cwnd based on pipeack.
>
> 2) At the start of FR we reset cwnd based on pipeACK, while
> at the end we further reduce pipeACK by the number of retransmissions.
>
> I posted it here for you consideration to be included in net-next.
>
> ---
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
prev parent reply other threads:[~2014-02-21 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 19:28 [PATCH 1/1] TCP NewCWV for Linux raffaello
2014-02-20 21:10 ` David Miller
2014-02-21 8:16 ` Zimmermann, Alexander [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=4C5CF805-D1A6-4DC1-B48F-F3D145C54C58@netapp.com \
--to=alexander.zimmermann@netapp.com \
--cc=gorry@erg.abdn.ac.uk \
--cc=netdev@vger.kernel.org \
--cc=raffaello@erg.abdn.ac.uk \
--cc=ziaul.hossain@abdn.ac.uk \
/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