From: David Miller <davem@davemloft.net>
To: yangpc@wangsu.com
Cc: edumazet@google.com, ncardwell@google.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND net-next v2 0/5] tcp: fix stretch ACK bugs in congestion control modules
Date: Mon, 16 Mar 2020 18:27:08 -0700 (PDT) [thread overview]
Message-ID: <20200316.182708.2275968776439275159.davem@davemloft.net> (raw)
In-Reply-To: <1584340511-9870-1-git-send-email-yangpc@wangsu.com>
From: Pengcheng Yang <yangpc@wangsu.com>
Date: Mon, 16 Mar 2020 14:35:06 +0800
> "stretch ACKs" (caused by LRO, GRO, delayed ACKs or middleboxes)
> can cause serious performance shortfalls in common congestion
> control algorithms. Neal Cardwell submitted a series of patches
> starting with commit e73ebb0881ea ("tcp: stretch ACK fixes prep")
> to handle stretch ACKs and fixed stretch ACK bugs in Reno and
> CUBIC congestion control algorithms.
>
> This patch series continues to fix bic, scalable, veno and yeah
> congestion control algorithms to handle stretch ACKs.
>
> Changes in v2:
> - Provide [PATCH 0/N] to describe the modifications of this patch series
Series applied, thanks.
prev parent reply other threads:[~2020-03-17 1:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 6:35 [PATCH RESEND net-next v2 0/5] tcp: fix stretch ACK bugs in congestion control modules Pengcheng Yang
2020-03-16 6:35 ` [PATCH RESEND net-next v2 1/5] tcp: fix stretch ACK bugs in BIC Pengcheng Yang
2020-03-16 21:19 ` Neal Cardwell
2020-03-16 6:35 ` [PATCH RESEND net-next v2 2/5] tcp: fix stretch ACK bugs in Scalable Pengcheng Yang
2020-03-16 21:25 ` Neal Cardwell
2020-03-16 6:35 ` [PATCH RESEND net-next v2 3/5] tcp: stretch ACK fixes in Veno prep Pengcheng Yang
2020-03-16 21:42 ` Neal Cardwell
2020-03-16 6:35 ` [PATCH RESEND net-next v2 4/5] tcp: fix stretch ACK bugs in Veno Pengcheng Yang
2020-03-16 21:46 ` Neal Cardwell
2020-03-16 6:35 ` [PATCH RESEND net-next v2 5/5] tcp: fix stretch ACK bugs in Yeah Pengcheng Yang
2020-03-17 1:27 ` 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=20200316.182708.2275968776439275159.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=yangpc@wangsu.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).