From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/1] RFC: Clarifying seq_ack_to_tap logic
Date: Fri, 3 Oct 2025 16:30:50 +1000 [thread overview]
Message-ID: <20251003063051.1127873-1-david@gibson.dropbear.id.au> (raw)
Prompted by the discussion on Stefano's recent TCP fixes, here's
change I think clarifies our logic. This goes on top of my linter
fixes (specifically the cppcheck suppression in the vicinity) but
before Stefano's TCP fixes.
Happy to have it folded into those TCP fixes, or reorganised around
them.
Stefano, please review my large comment. I'm confident on some of the
points in there, but not all of them.
David Gibson (1):
tcp: Clarify logic calculating how much guest data to ack
tcp.c | 68 ++++++++++++++++++++++++++++++++++++-----------------------
1 file changed, 42 insertions(+), 26 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-03 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 6:30 David Gibson [this message]
2025-10-03 6:30 ` [PATCH 1/1] tcp: Clarify logic calculating how much guest data to ack David Gibson
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=20251003063051.1127873-1-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).