From: David Miller <davem@davemloft.net>
To: raffaello@erg.abdn.ac.uk
Cc: netdev@vger.kernel.org, ziaul.hossain@abdn.ac.uk, gorry@erg.abdn.ac.uk
Subject: Re: [PATCH 1/1] TCP NewCWV for Linux
Date: Thu, 20 Feb 2014 16:10:15 -0500 (EST) [thread overview]
Message-ID: <20140220.161015.892943239767681091.davem@davemloft.net> (raw)
In-Reply-To: <bbf79368e5d6514fbe6704a77b473407.squirrel@blake.erg.abdn.ac.uk>
From: raffaello@erg.abdn.ac.uk
Date: Thu, 20 Feb 2014 19:28:56 -0000
> 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.
> 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.
You need to provide a proper signoff, please see
linux/Documentation/SubmittingPatches
next prev parent reply other threads:[~2014-02-20 21:10 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 [this message]
2014-02-21 8:16 ` Zimmermann, Alexander
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=20140220.161015.892943239767681091.davem@davemloft.net \
--to=davem@davemloft.net \
--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