From: nramaswamy@openai.com
To: Neal Cardwell <ncardwell.sw@gmail.com>
Cc: Neil Ramaswamy <nramaswamy@openai.com>,
edumazet@kernel.org, davem@davemloft.net, horms@kernel.org,
jiayuan.chen@linux.dev, kuba@kernel.org, kuniyu@google.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
ncardwell@google.com, netdev@vger.kernel.org, pabeni@redhat.com,
shuah@kernel.org, ycheng@google.com
Subject: Re: [PATCH net v2 1/2] tcp: restore RACK list membership when undoing loss
Date: Thu, 8 Oct 2026 14:20:01 -0700 [thread overview]
Message-ID: <20261008212007.11619-1-nramaswamy@openai.com> (raw)
In-Reply-To: <20261006141300.1722466-1-ncardwell.sw@gmail.com>
From: Neil Ramaswamy <nramaswamy@openai.com>
Hi Neal and Eric,
Thanks for the detailed replies. Neal's approach is much cheaper than my
original patch on a few UML microbenchmarks that I ran.
I'm not entirely sure I understand Eric's usage of "often" when he mentioned
the O(1) list splice, but the metrics that I've collected from my particular
repro seem to suggest that Neal and Yuchung's assumption about LOST but not
EVER_RETRANS segments holds in the cases I captured, so I'd be happy with that
approach.
(One super nit on the runtime complexity of it: in the comment for
tcp_tsorted_relink_skb we say that it's O(1) amortized time, but I think it's
more that during partial undo all relink calls together traverse the RACK list
at most once.)
For Neal's fix, I also did write up a small packetdrill that shows that segments
that are already retransmitted and then marked LOST are not added back to the
RACK list during partial undo, as intended. Happy to contribute that if useful
for explicitly documenting that this is behavior we are okay with.
How would you like to move forward here? Do you want me to fold this into a v3
patch with attribution tags or do you want to send a new patch yourself?
Neil
next prev parent reply other threads:[~2026-10-08 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 5:15 [PATCH net v2 0/2] tcp: preserve RACK tracking across partial undo nramaswamy
2026-10-06 5:15 ` [PATCH net v2 1/2] tcp: restore RACK list membership when undoing loss nramaswamy
2026-10-06 6:42 ` Eric Dumazet
2026-10-06 11:23 ` Eric Dumazet
2026-10-06 14:13 ` Neal Cardwell
2026-10-08 21:20 ` nramaswamy [this message]
2026-10-08 21:47 ` Neal Cardwell
2026-10-06 5:15 ` [PATCH net v2 2/2] selftests: net: packetdrill: test RACK after partial undo nramaswamy
2026-10-06 7:04 ` Eric Dumazet
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=20261008212007.11619-1-nramaswamy@openai.com \
--to=nramaswamy@openai.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ncardwell.sw@gmail.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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