From: Jakub Kicinski <kuba@kernel.org>
To: Neal Cardwell <ncardwell.sw@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Neal Cardwell <ncardwell@google.com>,
Yuchung Cheng <ycheng@google.com>
Subject: Re: [PATCH net-next v2 1/3] tcp: remove obsolete and unused RFC3517/RFC6675 loss recovery code
Date: Tue, 17 Jun 2025 16:19:48 -0700 [thread overview]
Message-ID: <20250617161948.3a0ae368@kernel.org> (raw)
In-Reply-To: <20250615001435.2390793-2-ncardwell.sw@gmail.com>
On Sat, 14 Jun 2025 20:14:33 -0400 Neal Cardwell wrote:
> + RACK: 0x1 enables RACK loss detection, for fast detection of lost
> + retransmissions and tail drops, and resilience to
> + reordering. currrently, setting this bit to 0 has no
currently ^
fixed when applying
> + effect, since RACK is the only supported loss detection
> + algorithm.
next prev parent reply other threads:[~2025-06-17 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 0:14 [PATCH net-next v2 0/3] tcp: remove obsolete RFC3517/RFC6675 code Neal Cardwell
2025-06-15 0:14 ` [PATCH net-next v2 1/3] tcp: remove obsolete and unused RFC3517/RFC6675 loss recovery code Neal Cardwell
2025-06-17 23:19 ` Jakub Kicinski [this message]
2025-06-15 0:14 ` [PATCH net-next v2 2/3] tcp: remove RFC3517/RFC6675 hint state: lost_skb_hint, lost_cnt_hint Neal Cardwell
2025-06-15 0:14 ` [PATCH net-next v2 3/3] tcp: remove RFC3517/RFC6675 tcp_clear_retrans_hints_partial() Neal Cardwell
2025-06-17 23:30 ` [PATCH net-next v2 0/3] tcp: remove obsolete RFC3517/RFC6675 code patchwork-bot+netdevbpf
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=20250617161948.3a0ae368@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ncardwell.sw@gmail.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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).