Thread (13 messages) 13 messages, 4 authors, 2026-02-26

Re: [PATCH RFC net-next 0/4] tcp: RFC 7323-compliant window retraction handling

From: Eric Dumazet <edumazet@google.com>
Date: 2026-02-24 09:22:34
Also in: linux-doc, linux-kselftest, lkml

On Mon, Feb 23, 2026 at 1:07 AM Simon Baatz [off-list ref] wrote:
Hi Eric,

On Fri, Feb 20, 2026 at 09:58:00AM +0100, Eric Dumazet wrote:
quoted
Hi Simon, thanks for the clean series.

I would guess you use some AI ? This is fine, just curious.
Thank you!  Yes, I’ve found AI helpful for getting familiar with a
new code base.  I also use it to refine or clean up the wording of
bigger commit messages.  Code generation works quite well for quick,
throw‑away code (like reproducers).
quoted
Can you add more tests, in memory stress situations ?

Like :

A receiver grew the RWIN over time up to 8 MB.

Then the application (or the kernel under stress) used SO_RCVBUF to 16K.

I want to make sure the socket wont accept packets to fill the prior
window and consume 8MB
I suspect generating 8 MB worth of RX data in packetdrill won't be
fun (unless there’s a trick I’m missing).  And using regular TCP
sockets on both ends would probably be rather uninteresting (no
packets sent once RWIN = 0)
8MB was only to show my point.

A packetdrill test reaching 1MB should be doable.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help