All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?VGltIEbDvGNoc2VsIDx0LmZ1ZWNoc2VsQGdteC5kZT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	ncardwell@google.com, kuniyu@google.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	fmancera@suse.de, ebiggers@kernel.org, bpf@vger.kernel.org,
	lukas.prause@ikt.uni-hannover.de
Subject: Re: [PATCHv10 net-next] tcp: Add TCP ROCCET congestion control module.
Date: Mon, 19 Oct 2026 23:20:08 +0000	[thread overview]
Message-ID: <179245200852.3379641.9369534757805507535.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <asdfdDIQb7Nhm692@volt-roccet-vm>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 8 Oct 2026 11:16:36 +0200 you wrote:
> TCP ROCCET is a new congestion control algorithm based on TCP CUBIC
> that improves its overall performance in cellular networks. By its mode
> of function, CUBIC causes bufferbloat while it tries to detect the
> available throughput of a network path. This is particularly a problem
> with large buffers in mobile networks. A more detailed description and
> analysis of this problem caused by TCP CUBIC can be found in [1].
> TCP ROCCET's main method of addressing the bufferbloat problem is by
> adding two additional metrics. The first metric is the relative increase
> in RTT from its minimum, the srRTT. Here, bufferbloat can be detected
> when RTTs increase due to buffer filling. The second metric is the
> acknowledgment arrival rate sampled over 100ms intervals and the bytes
> sent and received over 5 RTTs. If CUBIC increases the send rate or
> congestion window, and the acknowledgment arrival rate stays at the
> same level, the connection is limited by the bottleneck link's capacity.
> In such cases, ROCCET reduces the send rate to prevent bufferbloat.
> ROCCET uses a modified version of slow start rather than HyStart because
> HyStart is known to enter the congestion avoidance phase too early when
> used in cellular networks [2]. Therefore, ROCCET uses a combination of
> srRTT and the acknowledgment arrival rate to determine when to exit slow
> start. For the congestion avoidance phase, ROCCET relies on the srRTT and
> monitoring the sent and received bytes to detect the filling of the
> bottleneck buffer. To keep the minimum RTT updated, ROCCET performs
> minimum RTT probing if no new minimum RTT was found in the last 5 seconds.
> To this end ROCCET halves the cwnd and probes for 200ms but at least for
> one RTT, for a new minimum RTT. After probing, ROCCET refills the pipe
> carefully. In addition, ROCCET reacts to packet loss by adapting CUBIC's
> behavior. ECNs are handled as ROCCET congestion event, where the cwnd gets
> reduced and ROCCET enters a buffer drain state.
> 
> [...]

Here is the summary with links:
  - [PATCHv10,net-next] tcp: Add TCP ROCCET congestion control module.
    https://git.kernel.org/netdev/net-next/c/819d59638796

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-19 23:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  9:16 [PATCHv10 net-next] tcp: Add TCP ROCCET congestion control module Tim Fuechsel
2026-10-09  9:17 ` sashiko-bot
2026-10-10 10:18   ` Tim Füchsel
2026-10-12  9:37 ` netdev-bot+sashiko
2026-10-19 23:20 ` patchwork-bot+netdevbpf [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=179245200852.3379641.9369534757805507535.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?b?VGltIEbDvGNoc2VsIDx0LmZ1ZWNoc2VsQGdteC5kZT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=edumazet@google.com \
    --cc=fmancera@suse.de \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.prause@ikt.uni-hannover.de \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.