src/sys/netinet/cc, branch main

netinet: remove _WANT_INPCB and _WANT_TCPCB

2026-03-12T16:37:53+00:00

These were hacks since FreeBSD 12 that provided some transition period for
utilities to migrate from reading kernel memory via kvm(3) to sysctl(3)
based APIs.  The transition period is over.

netinet: Use proper prototype for SYSINIT functions

2025-10-13T10:12:33+00:00

MFC after:	1 week

mod_cc(4): Fix a typo in a source code comment

2025-08-25T08:39:11+00:00

- s/assigments/assignments/

MFC after:	3 days

cc_cubic: sync to the new specification of RFC9438 for TCP CUBIC.

2025-06-16T16:52:46+00:00

Reviewed by: rscheff
Differential Revision: https://reviews.freebsd.org/D49540

tcp cc: use tcp_compute_pipe() for pipe in xx_post_recovery() directly

2025-03-17T13:00:50+00:00

This follows up with commit 67787d200488, and obsoletes the non-default
pipe calculation from commit 46f584823798 nearly 25 years ago.

Reviewed by: rscheff
Differential Revision: https://reviews.freebsd.org/D49247

tcp: make inflight data (pipe) calculation consistent

2025-02-28T20:53:12+00:00

Reviewed by: glebius, rrs, tuexen
Differential Revision: https://reviews.freebsd.org/D49047

cc_cubic: remove redundant code

2025-02-20T16:00:41+00:00

During my progress on updating cc_cubic to RFC9438, found such redundancy as:

- W_est: we use the alternative stack local variable `W_est` in
	 `cubic_ack_received()`.
- cwnd_prior: it is used for Reno-Friendly Region in RFC9438 Section 4.3,
	 but we use the alternative cwnd from NewReno for Reno-Friendly as
	 in commit ee45061051715be4704ba22d2fcd1c373e29079d.

No functional change intended.

Reviewed by: rscheff, tuexen
Differential Revision: https://reviews.freebsd.org/D49008

cc_cubic: remove redundant calls of tcp_fixed_maxseg()

2025-02-12T22:49:21+00:00

Summary: No functional change intended.

Reviewed by: rscheff, tuexen

Subscribers: imp, melifaro, glebius

Differential Revision: https://reviews.freebsd.org/D48967

tcp: Use segment size excluding tcp options for all cwnd calculations

2024-11-14T09:16:57+00:00

Avoid sending small segments by making sure that cwnd is usually
calculated in full (data) segment sizes. Especially during loss
recovery and retransmission scenarios.

Reviewed By: tuexen, #transport
Sponsored by: NetApp, Inc.
Differential Revision: https://reviews.freebsd.org/D47474

tcp cc: Remove a stray semicolon

2024-10-24T15:04:50+00:00

MFC after:	1 week