mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: nramaswamy@openai.com
To: Eric Dumazet <edumazet@kernel.org>,
	Neal Cardwell <ncardwell.sw@gmail.com>
Cc: Neil Ramaswamy <nramaswamy@openai.com>,
	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 v3 3/3] selftests: net: packetdrill: test RTO fallback after partial undo
Date: Tue, 20 Oct 2026 20:32:19 -0700	[thread overview]
Message-ID: <20261021033310.46029-2-nramaswamy@openai.com> (raw)
In-Reply-To: <20261012012601.27658-1-nramaswamy@openai.com>

From: Neil Ramaswamy <nramaswamy@openai.com>

Hi Eric and Neal,

What would be the best next steps here? Happy to give you more time to
review if needed, but I can also 1) send another patch with Neal's
approach or 2) send a patch with my proposal to move lost segments that
meet RACK's criteria to the lost list to make the merge simpler.

I'm still unsure how best to handle the -ENOBUFS case I mentioned. If you
have a preferred approach, I can implement and test it.

Thanks.

  reply	other threads:[~2026-10-21  3:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09  5:00 [PATCH net v3 0/3] tcp: preserve RACK tracking across " nramaswamy
2026-10-09  5:00 ` [PATCH net v3 1/3] tcp: restore RACK list membership when undoing loss nramaswamy
2026-10-09  5:07   ` Eric Dumazet
2026-10-09  5:00 ` [PATCH net v3 2/3] selftests: net: packetdrill: test RACK after partial undo nramaswamy
2026-10-09  5:17   ` Eric Dumazet
2026-10-12  1:25     ` nramaswamy
2026-10-09  5:00 ` [PATCH net v3 3/3] selftests: net: packetdrill: test RTO fallback " nramaswamy
2026-10-09  5:47   ` Eric Dumazet
2026-10-09 17:14     ` Neal Cardwell
2026-10-10  6:25       ` Eric Dumazet
2026-10-12  1:25       ` nramaswamy
2026-10-21  3:32         ` nramaswamy [this message]
2026-10-21 13:36         ` Neal Cardwell

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=20261021033310.46029-2-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
all inboxes | Powered by JetHome®