From: Mingrui Zhang <mrzhang97@gmail.com>
To: edumazet@google.com, davem@davemloft.net, ncardwell@google.com,
netdev@vger.kernel.org
Cc: Mingrui Zhang <mrzhang97@gmail.com>, Lisong Xu <xu@unl.edu>
Subject: [PATCH net v4 0/3] tcp_cubic: fix to achieve at least the same throughput as Reno
Date: Sat, 17 Aug 2024 11:33:57 -0500 [thread overview]
Message-ID: <20240817163400.2616134-1-mrzhang97@gmail.com> (raw)
This series patches fixes some CUBIC bugs so that "CUBIC achieves at least
the same throughput as Reno in small-BDP networks"
[RFC 9438: https://www.rfc-editor.org/rfc/rfc9438.html]
It consists of three bug fixes, all changing function bictcp_update()
of tcp_cubic.c, which controls how fast CUBIC increases its
congestion window size snd_cwnd.
(1) tcp_cubic: fix to run bictcp_update() at least once per RTT
(2) tcp_cubic: fix to match Reno additive increment
(3) tcp_cubic: fix to use emulated Reno cwnd one RTT in the future
Experiments:
Below are Mininet experiments to demonstrate the performance difference
between the original CUBIC and patched CUBIC.
Network: link capacity = 100Mbps, RTT = 4ms
TCP flows: one RENO and one CUBIC. initial cwnd = 10 packets.
The first data packet of each flow is lost
snd_cwnd of RENO and original CUBIC flows
https://github.com/zmrui/tcp_cubic_fix/blob/main/renocubic_fixb0.jpg
snd_cwnd of RENO and patched CUBIC (with bug fixes 1, 2, and 3) flows.
https://github.com/zmrui/tcp_cubic_fix/blob/main/renocubic_fixb1b2b3.jpg
The result of patched CUBIC with different combinations of
bug fixes 1, 2, and 3 can be found at the following link,
where you can also find more experiment results.
https://github.com/zmrui/tcp_cubic_fix
Thanks
Mingrui, and Lisong
Changes:
v3->v4:
replace min() with min_t()
separate declarations and code of tcp_cwnd_next_rtt
https://lore.kernel.org/netdev/20240815214035.1145228-1-mrzhang97@gmail.com/
v2->v3:
Correct the "Fixes:" footer content
https://lore.kernel.org/netdev/20240815001718.2845791-1-mrzhang97@gmail.com/
v1->v2:
Separate patches
Add new cwnd_prior field to hold cwnd before a loss event
https://lore.kernel.org/netdev/20240810223130.379146-1-mrzhang97@gmail.com/
Signed-off-by: Mingrui Zhang <mrzhang97@gmail.com>
Signed-off-by: Lisong Xu <xu@unl.edu>
Mingrui Zhang (3):
tcp_cubic: fix to run bictcp_update() at least once per RTT
tcp_cubic: fix to match Reno additive increment
tcp_cubic: fix to use emulated Reno cwnd one RTT in the future
net/ipv4/tcp_cubic.c | 22 +++++++++++++++++-----
1 file changed, 17 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2024-08-17 16:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 16:33 Mingrui Zhang [this message]
2024-08-17 16:33 ` [PATCH net v4 1/3] tcp_cubic: fix to run bictcp_update() at least once per RTT Mingrui Zhang
2024-08-19 9:00 ` Eric Dumazet
2024-08-19 20:36 ` Mingrui Zhang
2024-08-20 12:53 ` Eric Dumazet
2024-08-25 17:47 ` Mingrui Zhang
2024-08-26 9:25 ` Eric Dumazet
2024-08-28 20:32 ` Neal Cardwell
2024-09-30 16:24 ` Eric Dumazet
2024-08-17 16:33 ` [PATCH net v4 2/3] tcp_cubic: fix to match Reno additive increment Mingrui Zhang
2024-08-19 8:22 ` Eric Dumazet
2024-08-19 21:03 ` Mingrui Zhang
2024-08-20 12:56 ` Eric Dumazet
2024-08-20 14:22 ` Mingrui Zhang
2024-08-17 16:34 ` [PATCH net v4 3/3] tcp_cubic: fix to use emulated Reno cwnd one RTT in the future Mingrui Zhang
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=20240817163400.2616134-1-mrzhang97@gmail.com \
--to=mrzhang97@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=xu@unl.edu \
/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).